1
Map the C# repository
Codna builds a dependency and blast-radius graph of the repository from its import patterns. No model call, zero tokens.
C#
Fix C# bugs with Codna
Codna maps your C# solution for zero tokens, fixes from evidence, and runs dotnet test until it passes.
The problem
An async deadlock in one test is a blocking call in another project.
Codna builds a dependency and blast-radius graph of the repository from its import patterns. No model call, zero tokens. using directives and project references are the edges, so the agent follows the awaited call chain from the failing xUnit test to the blocking call.
How Codna fixes it
How Codna fixes it
2
Fix from evidence
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.
3
Verify with dotnet test
Run codna fix --tests --apply and Codna runs your tests in a sandbox and re-fixes until they pass, up to the iteration limit you set. Set fix.test_command in codna.yaml, or pass --test-cmd, when your runner is not pytest. 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.
pip install codna codna fix . --issue "OrderService.ProcessAsync deadlocks under load" --tests --apply --test-cmd "dotnet test --logger \"junit;LogFilePath=$CODNA_JUNIT\""
What you get
Built for C#
dotnet test as the oracle
Use the JUnit logger and set fix.test_command or pass --test-cmd.
C#-aware recall
On-device recall parses .cs files with tree-sitter.
Multi-project solutions
The map spans the solution; Codna reports the blast radius across projects.
The proof
Fewer tokens. Faster. Verified.
Frequently asked
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, through dotnet test with a JUnit logger. Set fix.test_command or pass --test-cmd.
The map follows using directives and project references; the bundle carries the call paths. Your tests verify the behaviour.
The map spans the solution. Package boundaries are edges; Codna reports blast radius across projects.
Codna ships as a CLI, an MCP server for Cursor and Claude, a GitHub Action (thyn-ai/codna-action@v1) and a GitHub App that reviews every pull request and opens fix PRs from a label, a comment or a red check.
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.
Related
