Turn your product into self-improving software.

Set a goal, give it context, and connect your data sources. Tekk spawns a 24/7 team of expert agents that loop over your codebase, research the best solutions, and constantly improve your software.

A 24/7 team of agents

Tekk spawns a specialist for every part of your product.

Set a goal. Tekk spawns an expert agent for each part of your product — security, performance, your AI, architecture, your data. Each one runs its own loop over your code around the clock, and writes a spec the moment it sees a way to make your product better.

goal: ship a stable v1
tekk.
Security
secrets · vulns · deps
watching…
Engineering
retrieval · evals · quality
watching…
Performance
queries · latency · N+1s
watching…
Architecture
structure · coupling · drift
watching…
The spec, in the loop

From issue tracking to problem solving.

A ticket in most tools is one line of text. In Tekk it's a worked-out spec — proposed by a loop or written by you. Tekk reads your code, your data, and the web, then writes what your team can actually build.

Your codebase Web research Your live data
Upgrade retrieval to hybrid search + rerankingspec
TL;DR
Plain vector search misses results users expect — answers are weak on multi-term queries.
What we're building
Hybrid search (keyword + vector) with a reranking pass before the model sees results.
Acceptance criteria
  • Recall@10 beats the current setup on the eval set
  • Reranking adds under 150ms at p95
  • Falls back to vector-only if the reranker errors
Out of scope
Re-embedding old docs, query rewriting, graph RAG
Files
src/agent/retrieval.ts · src/db/search.ts

Same for every ticket — proposed or hand-written. The spec is always authored in the loop.

Under the hood · plan & coordinate

And it's where your team gets the work done.

A loop writes the spec for you — or you write one by hand when you already know what you want. Either way it lands on your board: prioritize, assign, track it to done.

app.tekk.coach
Tekk.coach board — specs, goals, and todo / in-progress / done columns
Auto: the loops fill your board Manual: plan a spec yourself Together: assign, prioritize, ship
Inside one agent · the spec loop

Search the code. Design the change. Write the spec. Repeat.

Every agent runs the same loop in the background. Nothing reaches you until it's passed the agent's own critic.

01 GOAL
Reads your goal
What it's working toward
02 SEARCH
Searches your codebase
Semantic · grep · history
03 RESEARCH
Researches the web
Current best practices
04 DRAFT
Designs the change
Grounded in your code
05 CRITIC
Critiques its own work
Only survivors reach you
06 SPEC
Emits a spec
You approve · team builds
Then it loops.
Every change you ship is the next signal.
Where Tekk stops

Tekk proposes. You decide. Your team builds.

It finds what's worth doing and writes the spec — checked by its own critic first. No black box, no autopilot, no surprise commits.

Build it with anything

Works with the coding agents you already use.

Tekk writes the spec. Hand it to any coding agent — or build it yourself. No lock-in.

Claude Code Cursor Codex Gemini CLI Copilot Windsurf

The spec is just markdown — it works with whatever ships next, too.

Put Tekk on your codebase.

Connect your repo, set a goal, and wake up to proposals worth reviewing — each one a spec your team can pick up.

Connect your repo →