See what changed. Understand why it passed—or failed.
Follow a pagination repair that coordinates record revisions, deletions and page boundaries. Then inspect a configuration patch whose remaining defects prevent acceptance. Each example shows the original code, the goal, the proposed changes and the observed checks.
2 min 30 sec · On-screen annotations · Local Chatterbox synthetic narration. Recorded from the public app using saved real Nebius Token Factory runs, checked in isolated local Docker containers.
Watching this recording and opening its saved examples makes no new model calls. Generate patch starts a new live attempt. The examples demonstrate the workflow; they do not establish a benchmark advantage or correctness for every possible input.
Read the narration transcript
- 0:00 · Start with the code and the goal
Patch Proof checks AI code repairs before you use them. Choose a maintenance task. Read the starting source alongside its requirements and concrete examples. These are the actual files and behavior the model will work with.
- 0:13 · A real model proposes. Fixed checks decide.
Generate patch makes a real request through Nebius Token Factory. An isolated local Docker runner checks the code against fixed expected results. The model can edit allowed source files, but it cannot rewrite those checks.
- 0:28 · Pagination repair: stop repeating records
An activity browser pages through revised records. After cursor B, the next page should contain only C. The original helper repeats B and incorrectly claims another page exists.
- 0:40 · Review the proposal across cooperating helpers
The proposal coordinates three fixes: choose the latest revision before filtering deletions, resume strictly after the cursor, and calculate whether more records remain. Review the changed lines alongside preserved context.
- 0:54 · From 16 of 22 to all 22 checks passing
The starting code passed sixteen of twenty-two checks. This proposal passes all twenty-two. The next page contains only C, with no next cursor. Checks also cover revisions, validation, and preserving the original inputs.
- 1:09 · A passing result still needs your review
All the declared checks now pass. You still inspect the change before using it. Passing these cases does not prove correctness for every possible input. Patch Proof does not merge the patch automatically.
- 1:23 · Failed repair: configuration overlays
This configuration helper combines deployment settings. Lists must be replaced, and the change report must identify precise nested paths. The original code wrongly appends regions and reports only the parent setting.
- 1:38 · The proposal improves one part of the behavior
The patch now replaces the regions list. But the change-reporting helper still records its parent object. The diff shows the edits beside unchanged context and original line numbers.
- 1:50 · 17 of 22 checks pass. Five still fail.
Seventeen of twenty-two checks passed. This configuration is now correct, but its change report still says service instead of service dot timeout. Five checks remain failed.
- 2:02 · Functional failures, followed by a timed-out attempt
A later attempt hit the five-minute time limit before its checks could finish. The result is an execution error, with no accepted repair. Earlier failures remain visible.
- 2:14 · Take the evidence into your review
Download the evidence to keep the starting source, proposals, recorded results, logs, and accounting together. These walkthroughs show saved real runs. To make a new attempt, return to Try a repair and select Generate patch.