Today's coding agents read your repo through the model.
They open file after file inside the context window to find the bug. That costs tokens and time. And it forgets between runs.
80,971average tokens per fix for Cursor on the same 87 cases.
codna · Understand. Fix. Evolve.
Agents read your code. Codna understands it.
Codna maps your entire repo for zero tokens, then sends an agent in with only the evidence it needs.
pip install codnaRuns on your machine or your cloud. Your code never leaves without your key.
$ codna fix https://github.com/org/repo --issue "checkout test failing" --open-pr
✓understood org/repo · 0 model tokens
→root cause: session race in checkout.ts
→symbol: Checkout.finalize · blast radius: 3
→context: raw → bundle tokens (N× smaller)
✓confidence · regression risk · opened pull request
$
5×fewer tokens than Cursor
1.7×faster than Cursor
$0.02per verified fix
0tokens to understand
Measured on 87 matched bug-fix cases against Cursor: 5× fewer tokens, 1.7× faster, 87 of 87 fixes verified.
Codna understands first, then acts.
Codna maps every symbol, dependency and blast radius for zero model tokens. Then it hands the agent an evidence bundle scoped to the issue and prints the raw-to-bundle size on every run. Codna remembers, too: recall runs on Telys, our on-device memory engine.
16,159average tokens per fix for Codna. 87 of 87 verified.
Memory
Codna doesn't forget your codebase.
A deterministic graph maps structure for zero tokens. Telys, our on-device memory engine, recalls the relevant code without a cloud round-trip. Together they hand the agent a smaller evidence bundle, and the memory persists across sessions.
Proof: structure + recall, measured
Deterministic graph for structure. Telys for on-device recall. Measured on 87 matched bug-fix cases against Cursor.
0cloud round-trips for recall
5×fewer tokens per fix
87 / 87fixes verified
11languages in on-device recall
How it works
One pass, start to finish.
The agent does not wander through your repo. Codna gives it a map, evidence, and a safe path to ship.
Understand
Codna parses your repo into a dependency and blast-radius graph. No model. Zero tokens.
Fix
It names the suspect files, packs the evidence bundle, and runs the agent with root cause and confidence attached.
Evolve
Every fix reports blast radius and regression risk, and passes a risk gate before it is applied or a pull request opens.
Benchmarks
Faster. Cheaper. Verified.
Head-to-head with Cursor on 87 matched bug-fix cases, identical checkouts. Codna used fewer tokens, ran faster, and verified every fix.
| Codna | Cursor | |
|---|---|---|
| Fixes verified · 87 cases | 87 / 87 | 87 / 87 |
| Average wall time | 13.4s | 22.6s |
| Average tokens per fix | 16.2K | 81.0K |
5×fewer tokens per fix than Cursor.
1.7×faster per fix than Cursor.
$0.02per verified fix, averaged over the 87 cases.
Every case counted only when the fix verified. Full table on the benchmarks page.
Any language your repo imports · zero tokens
Codna builds its repository map from import patterns in any language — Python, TypeScript, Go, Rust, Java and more — for zero tokens.
Workflow
Built into your workflow.
One command, one GitHub App, one Action, or one MCP server. Codna sits where your engineering team already works.
One command.
codna fix . in any repo. Or codna triage . to understand it for zero tokens.
codna triage . codna fix . --issue "checkout fails"
In your editor.
Add Codna to Cursor or Claude as an MCP server. Five tools: triage, fix, secure, recall, and report.
Native GitHub App.
Codna reviews every pull request, opens a fix from an issue label, a comment or a red check, and leaves the merge to you.
A patch you can trust.
Every fix comes with root cause, confidence, blast radius, and regression risk.
Runs on your machine.
Bring your own model key.
Secret redaction. Always on.
Fail-closed egress when you set it.
Private by design
Your code is yours.
Understanding runs on your machine and spends no model tokens. Only the evidence bundle reaches your model provider, with your key. Secrets are redacted, and that cannot be turned off. Set privacy.egress to fail-closed and Codna runs your tests only under kernel-level network denial.