Loading demos
An agent that reads the repo, writes the patch and proves it with tests.
Read the repo. Change the code. Prove it. · Sample workspace included
$ inspect src/services/runs.tsFound retry state dropped after timeout$ apply minimal state transition patch✓ 18 tests passed · typecheck clean @@ retryRun(runId)− return execute(runId)+ return execute(runId, { preserveAttempt: true })median across accepted patches
on first review
for reproducible bugs
Each feature is represented with real states and an integration seam that can be replaced without redesigning the UI.
Search code, instructions and history before proposing a change.
Review the intended files and validation steps before the agent starts writing.
Attach lint, type, test and build output to the patch instead of saying it should work.
Show the diff, risks and unresolved decisions where an engineer can act on them.
The same four-stage narrative appears in the product timeline, logs and analytics.
Turn the report into a failing check or concrete observation.
Follow the owning code and nearby contracts.
Make the smallest coherent change.
Run targeted checks and report evidence with the diff.
“A patch with a failing test turned green is worth more than a page of plausible suggestions.”
Start with this workflow and tailor it to your team, tools and operating model.
No card required · 14-day trial · Cancel any time