What Nemotron found
Loading the recorded diagnosis…
What it changed
NVIDIA Nemotron
- Model time
- —
- Total tokens
- —
- This successful call
- 1 · not cached
KEYBOARD & FORM BUGS · NVIDIA NEMOTRON ON NEBIUS · REAL BROWSER VERDICT
Repair the task.
Keep the outcome.
Tabstitch fixes keyboard accessibility and form bugs in web components, the kind that stop someone using only a keyboard from finishing a task. NVIDIA Nemotron on Nebius Token Factory writes the patch. A real browser then replays the user's task, and the patch is accepted only if the task passes, the submitted data stays the same and no guarded behaviour breaks. It was tested on real bugs that the maintainers of Bootstrap, GOV.UK Frontend and other libraries fixed by hand.
ACTUAL RUNTIME REPAIRNVIDIA NemotrononNebius Token FactoryRecorded runs make no model call · Run it live on any bug: GitHub Actions calls Nemotron and replies on an issue
HOW A PATCH IS ACCEPTED
The model proposes.
The browser decides.
- 01
Freeze the contract
The same keys, the data the form must submit, an independent pointer path and regression guards that already pass.
- 02
Let Nemotron propose
Nemotron 3 Super edits the library source in a disposable copy. If the browser rejects the patch, Nemotron 3 Ultra gets the exact failure and tries again.
- 03
Make the browser decide
Replay every path in a fresh browser. Reject a patch that passes the task but changes the submitted data or breaks a guarded behaviour.
ONE TASK. THE SAME KEYS. TWO OUTCOMES.
Follow the focus.
Step through the actual browser captures.
Enter
Open the dialog
Loading the measured focus transition…
FOCUS—
FOCUS—
Same task. Independent verdict.The model writes a proposal. Browser execution decides whether it works.
Use your own keyboard on the exact recorded source:Try original ↗Try repaired ↗The recorded source, served as captured. Opening it makes no model call.
MODEL-AUTHORED SOURCE. EXECUTION-OWNED VERDICT.
A patch you can question.
ACTUAL SOURCE DIFFDownload patch ↓
Loading source diff…
Model and published human fix
View pinned upstream commitBoth columns below compare the same pinned runtime JavaScript. The original upstream change is TypeScript; its verbatim source diff is linked separately. These review derivatives leave the archived proof unchanged.
MODEL · contextual diff
PUBLISHED HUMAN FIX · runtime reconstruction
What had to stay true
The repair cannot rewrite these checks.
- Loading the frozen journey and functional checks…
What this pass does and does not establish
Each recording verifies only its frozen journey and recorded conditions. It does not establish a repair success rate, full WCAG conformance or real screen-reader support.
See the failed attempts, too
The historical case took three calls: one output was truncated, one invented an unapproved file and was rejected, and one passed. The synthetic checkout took one successful call. These are development attempts on two known cases, not an independent benchmark.
INSPECT THE RECORDING
The evidence travels
with the result.
No API key needed. These files come from the recorded run. The complete proof includes browser captures, focus states, source changes and the frozen task.
Download complete proof ↓Model response Raw output, reasoning and request ID ↗Frozen journey Exact keys and expected results ↗Verification Verdict, scope and rejection reasons ↗Artifact manifest SHA-256 hashes for integrity checking ↗
Hashes detect changed files; they do not certify the publisher or replace independent execution.
Run a fresh browser journey.
Select your static application, capture and freeze the task, then let Nemotron repair an isolated copy. Verify a human edit with added, deleted or modified files in the same flow.