1
Map for zero tokens
Codna builds a dependency and blast-radius graph of the repository from its import patterns. No model call, zero tokens.
Comparison
Codna vs Sourcegraph Amp / Cody
Amp and Cody are coding agents with code search behind them. Codna maps the repository deterministically for zero tokens, fixes from evidence, and reports root cause, confidence and regression risk.
The problem
Search finds candidates. A fix needs the cause.
Codna turns the repository into a dependency and blast-radius graph, then hands the agent the suspect files and call paths for this issue. The result is a fix with root cause and risk attached, not a list of places to look.
How Codna fixes it
How Codna works
2
Hand over evidence, not the repo
The agent receives an evidence bundle scoped to the issue: the suspect files, the call paths, the failing test. Codna prints the raw-to-bundle token size on every run.
3
Report, gate, open the PR
Every fix reports root cause, confidence, blast radius and regression risk, and passes a risk gate before it is applied or a pull request opens. With --open-pr, or through the GitHub App, the pull request states the issue, the root cause, the symbols touched and a confidence score, and asks for review before merging. Codna never merges.
codna fix . --issue "regression after the search-indexer refactor"
What you get
What you get
A deterministic map
Codna builds a dependency and blast-radius graph of the repository from its import patterns. No model call, zero tokens.
Every fix explained
Every fix reports root cause, confidence, blast radius and regression risk, and passes a risk gate before it is applied or a pull request opens.
About $0.02 per fix, measured
On 87 matched bug-fix cases against Cursor, Codna averaged 16,159 total tokens and about $0.02 of model spend per verified fix, 5× fewer tokens and 1.7× faster. With your own key you pay your provider directly.
The proof
Fewer tokens. Faster. Verified.
Frequently asked
The only measured head-to-head Codna publishes is against Cursor: 87 matched bug-fix cases on identical checkouts, 5× fewer tokens, 1.7× faster, 87 of 87 verified, about $0.02 per fix. Everything else on this page describes Codna's own behaviour, not Sourcegraph Amp / Cody's internals.
Codna is a fix, review and secure tool with a deterministic map underneath. Use it alongside whatever you use to search code.
Codna builds a dependency and blast-radius graph of the repository from its import patterns. No model call, zero tokens. The agent receives an evidence bundle scoped to the issue: the suspect files, the call paths, the failing test. Codna prints the raw-to-bundle token size on every run. Every fix reports root cause, confidence, blast radius and regression risk, and passes a risk gate before it is applied or a pull request opens.
Yes. Codna is a CLI, an MCP server, a GitHub Action and a GitHub App. Add it where it helps and keep the rest of your workflow.
Bring a key from Anthropic, OpenAI, Google Gemini, Groq, Mistral, OpenRouter or xAI, stored in your OS keychain with codna key set, or sign in and use the managed allowance. The repository map is built from import patterns, so it is not tied to one language. On-device recall covers Python, JavaScript, TypeScript, Go, Rust, Java, C, C++, C#, PHP and Ruby. Your own test command verifies the fix.
Understanding runs on your machine and spends no tokens. Only the evidence bundle or the diff reaches your model provider, with your key from the OS keychain. Set privacy.egress to fail-closed in codna.yaml and Codna runs your tests only under kernel-level network denial. Secret redaction is always on. On 87 matched bug-fix cases against Cursor, Codna averaged 16,159 total tokens and about $0.02 of model spend per verified fix, 5× fewer tokens and 1.7× faster. With your own key you pay your provider directly.
Related
