What Codna fixes.
Real engineering problems. One flow every time: map the repo for zero tokens, fix from evidence, report root cause and risk, open a pull request you review.
Use cases
Fix flaky tests
A retry hides a flaky test. Codna finds the shared state or ordering it depends on, fixes the cause, and re-runs your tests until they pass.
From Sentry alert to fix PR
Paste the alert into codna fix, or label the GitHub issue codna-fix. Codna follows the call paths the trace names and opens a pull request with root cause attached.
Fix CI failures
A red check suite on a pull request triggers Codna. It triages the failure first, then opens a fix on the pull request branch with root cause attached.
Fix monorepo bugs
A shared package changes and three apps break. Codna maps the workspace for zero tokens, fixes with the consumers in view, and lists the tests the diff can affect.
Fix bugs in legacy code
No docs, few tests, and nobody remembers why. Codna maps the code for zero tokens, shows what a change reaches, and fixes with root cause and risk attached.
Fix breakage from a dependency upgrade
An upgrade breaks the build in one place and behaviour in three others. Codna maps every call site for zero tokens, fixes with them in view, and re-runs your tests.
Prove and fix scanner findings
Your scanner reports fifty findings. codna secure proves which are reachable, for zero model tokens, and the GitHub App comments the result on the issue or alert.
Fix a regression
It passed last release. It fails now. Codna maps the code for zero tokens, fixes the cause rather than the symptom, and reports the regression risk of the fix itself.
Understand a new codebase
New repo, first day. codna triage maps it for zero tokens and names the code an issue touches. Recall runs on-device. Nothing changes until you say so.
Fix Java bugs
Codna maps your Java project for zero tokens, fixes from evidence, and runs your Maven or Gradle tests until they pass.
