loading
loading
Point it at a repo and a benchmark. It bisects the history, explains the regression in plain English with the lines to prove it, and verifies a fix in a sandbox before it tells you it's done.
Example result from a recorded run:
A recorded example. The live terminal streams the same kind of events from your own job — every git call, sandbox run and Nemotron reply — as they happen.
Nothing here is a black box. Every stage produces something checkable — a commit hash, a cited diff, a before/after number — before the next one starts.
Binary-searches the commit history in isolated sandboxes until it lands on the exact commit where the benchmark got worse.
Reads the guilty diff in full file context and names the root cause — N+1 queries, a lost cache, an O(n²) creeping in — citing the exact lines responsible.
Proposes a patch, applies it in a fresh sandbox, and re-runs the benchmark. Nothing is called "fixed" until a real re-run proves it.
A fix is only marked resolved once a sandbox re-run actually recovers the benchmark. If it doesn't, you still get the honest diagnosis — not a fabricated success.
A git URL and a benchmark command. The commit range is optional.