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 Codex CLI
The Codex CLI is an agent you drive from the terminal. Codna understands the repository first, for zero tokens, then fixes from evidence and explains the result.
The problem
Reading the repo through the model costs tokens before any fix.
An agent that finds the bug by opening files inside the context window spends its budget on orientation. Codna moves that work out of the model: the dependency and blast-radius graph is built deterministically, and the agent starts with the evidence already in hand.
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 "the checkout test is failing"
What you get
What you get
Understanding for zero tokens
codna triage prints the suspect files and the raw-to-bundle context size without a model call.
A fix that explains itself
Root cause, confidence, blast radius and regression risk on every fix.
Your key, your model
Use OpenAI or any other supported provider with your own key, or the managed allowance.
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 the Codex CLI's internals.
Codna is a CLI, an MCP server, an Action and a GitHub App. You can run codna fix from the same terminal, or keep the Codex CLI for interactive work and let Codna review pull requests and open fix PRs.
Codna separates understanding from fixing. 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.
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
