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.
Use cases
Run a dependency upgrade across services
An upgrade touches many services, and each one can break in its own way.
- You ask Codex
/antinuous Upgrade our services to the new major version of this library. Run each service's tests and list the ones that fail, with the error and a suggested change.
Codex hands it to Antinuous.
- What it does
- Antinuous reads each service's code and dependencies.
- It applies the upgrade to every service in parallel.
- It runs each service's tests and collects the failures.
- It writes a table with one row per service and the suggested change.
- You get
A table with the upgrade status of each service and the changes it needs.
- Upgraded library
- API service
- Job workers
- Web app
- Command line tool
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
Kernel optimization
Run your code change tests on Antinuous.
Start with our agent, or connect your own to the same compute, orchestration, and simulation.
