Documentation

Understand Tekk

Tekk is your agent for self-improving software — it keeps a spec board, runs autonomous improvement loops on your codebase, and proposes work for you to greenlight. These docs explain the mental model, how to connect your own tools, and how to drive Tekk from inside your coding agent.

Connect

MCP server Connect Tekk to Claude Code, Codex, or Cursor and work your spec board from inside your coding agent — list specs, implement them, review proposals, read context.

Getting started

What Tekk is The one-page mental model — an AI CTO that keeps a spec board, runs improvement loops on your codebase, and proposes work for you to greenlight. Core concepts The Tekk vocabulary defined once — workspace, project, spec, goal, proposal, and loop — and how they fit together.

How it works

How the loops work The autonomous side of Tekk — what triggers a loop, how a proposal becomes a spec, and where you stay in control. Integrations Connect your own SaaS tools through Composio so Tekk can see production signals and act on them — Sentry first, more to follow. Pull requests Link GitHub pull requests to your specs so a spec shows what shipped it — and let a merge move the spec to done on its own, gated by its own checklist.

Stop prompting. Start shipping.

Connect your repo. Describe the problem. Get a spec your agents can execute.