Software engineering
Antinuous reads your repository, writes candidate changes, and runs your test suite on each one in its own workspace. It reports which changes pass and links each result to the code behind it.
A code change with removed lines in red and added lines in green, beside a branch graph
Use cases
Try several fixes for a failing test
A bug can have several plausible fixes, and each one needs a full test run.
- You ask Antinuous
This test started failing after last week's change. Propose a few fixes, run the full test suite on each, and tell me which pass and what each one changes.
- What it does
- Antinuous reads the repository and the failing test from GitHub.
- It writes several candidate fixes, each in its own workspace.
- It runs the full test suite on every candidate.
- It reports which fixes pass, with a diff for each.
- You get
A report with each candidate fix, its diff, and its test results.
Each candidate fix runs the full test suite in its own workspace.
- Read the failing test
- Write candidate fixes
- Run the tests on each
- Compare the passing fixes
Who it's for
- Software engineers
Try several fixes for a bug and keep the ones that pass.
- Engineering leads
Compare approaches to a change with test results for each.
- Platform engineers
Run an upgrade across many services and see which fail.
Works with
More in compute and hardware
A GPU die with twelve compute units coloured by how busy they are, a cache band, and memory stacks at each side
Kernel optimization
Run your code change tests on Antinuous.
Start with our agent, or connect your own to the same compute, orchestration, and simulation.
