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
Getting started
What Tekk is The one-page mental model — loops that watch your codebase, propose improvements for you to greenlight, and keep a board of specs your coding agent builds. Core concepts The Tekk vocabulary defined once — workspace, project, spec, goal, proposal, and loop — and how they fit together. Plans and models Two plans, the same credits and the same sixteen loops. Business runs on frontier models from Anthropic and OpenAI. AI Sovereignty runs everything on European AI, served in the EU by Melious and Mistral, and sends no AI request to a US provider.
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. Loops and their skills The sixteen loops Tekk can run on your project, the skills each one carries, and how a run picks the one method it will work with. Integrations Connect the tools where your software runs — Sentry, Datadog, PostHog, Stripe, Supabase and more — so loops can see production signals and investigate them. Read-only by default; every connector makes a loop sharper, and only Customer feedback needs one. 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.
Let your product improve itself.
Connect your repo. Sixteen loops start watching your code and bring you proposals — you greenlight them, your coding agent builds them.