Docs
How it works
Unfix doesn't write code. It judges a fix.
Reproduce the bug first
You reproduce the bug first (unfix bug or /bug): Unfix records the failure signature and how often it fails.
Independent checks
Each fix goes through independent checks:
- builds before and after the fix;
- the bug is there before the fix;
- the bug is gone after the fix (repeated runs);
- all other tests still pass;
- the fix does not weaken or delete tests;
- with the fix removed, the bug comes back.
Where the checks run
Builds and tests run in a Linux container on your machine. No cloud, no LLM in the verdict.
Verdicts
A single fix (/fix) gets one verdict:
VERIFIEDThe bug is fixed, with evidence.
REJECTEDNot fixed, or masked.
NOT VERIFIABLEEvidence can't decide.
Per-test regression verdicts for /check
FIXEDThe test failed before the change and passes now.
BROKENThe test passed before and fails with the change.
FLAKY ON THE BENCHThe test is unstable without the change too; fix the rig before trusting any result.
FLAKY, WORSEIt was flaky before, and the change makes it significantly worse.
Firmware
On STM32 NUCLEO boards via ST-Link, the checks run on the board.
Get the beta
Unfix 0.1 is in private beta for C/C++ and firmware teams. Email hello@unfix.dev with:
- company,
- what you build,
- OS,
- whether you test on real boards, and
- which AI coding agents you use.
We'll send the install kit and set up a short call.
Get the betahello@unfix.dev