Repairing failed extracts

Let the Browser Use agent diagnose a failed extract, then promote a checked fix yourself.

When a site changes its layout, an extract can start failing with SCHEMA_CHANGED. Repair lets the Browser Use agent look at the live page and propose a fix. Nothing changes until you promote it.

Works on public extracts that you ran with assertions (the fields you expect).
The agent proposes; Frankensurf checks the proposal against the saved failure and a fresh live read before you can use it.
You promote or disable a fix with one command, and can roll it back.

How it works

Run an extract with assertions. When it fails, the result carries a recovery object with a trace ID, and Frankensurf keeps a private copy of the failure.
Diagnose. The agent inspects the current page and proposes exact CSS selectors for each asserted field.
Terminal window
```
frankensurf repair TRACE_ID
```
Check. Frankensurf tests the proposal against the saved failure and runs an independent live read through another provider. The result records both, with timing and cost.

Promote. Turn the checked fix on by its ID and hash.

frankensurf repair-promote PROPOSAL_ID --proposal-sha256 SHA256

A promoted fix only applies to the same URL, adapter version and assertions, and only after the original adapter fails. Turn it off at any time:

frankensurf repair-disable PROPOSAL_ID --disable-reason "layout changed again"

Limits

Public reads only. Signed-in reads, actions and purchases are never repaired.
The agent never writes to a site, sees a secret or runs its own code.
Route proposals are recorded but can’t be promoted yet.