Background browser recovery
Let a background browser habit recover a changed route, then review its proposed steps before saving them.
last updated
Background browser recovery helps an eligible browser habit find a changed route. It is a separate opt-in for that habit. The current beta supports only reviewed built-in pages; Chrome session import and real websites remain unavailable.
Turn it on
In a browser habit's details, enable Allow AI recovery for this habit. For the built-in example, open Settings → General → Chrome background check and choose Test AI recovery, then review the normal run approval.
How recovery works
If an eligible navigation step fails, Plainwork offers the model a small list of currently available controls. The model chooses a control, and Plainwork checks it before asking you to approve the action in the live run panel.
Recovery can take several steps, but it must satisfy the original goal. It stays in the same temporary browser and cannot open foreground Chrome or switch to Guide via Screenshots. Unknown action outcomes, account or permission failures, and unsupported operations stop the run.
Each run permits one recovery attempt, limited to five model turns, four actions and sixty seconds. Rejecting an action or cancelling stops recovery and cleans up the browser.
What the model receives
Recovery sends the fixed goal and offered control identifiers and labels through Plainwork's existing cloud model service. It sends no screenshots, full page text, raw DOM, form or hidden values, cookies, storage dumps, or token-bearing URLs. Raw prompts and replies are not saved in the habit or run history.
Enabling recovery does not grant ongoing run approval or permission to import a Chrome session.
Review an improvement
After successful recovery, Review browser improvement shows the steps before and after. Accept improvement saves the validated steps; future successful runs replay them without a model. Reject improvement keeps the original habit. Use Replay saved habit to test the accepted fixture steps in a fresh browser.
If the habit changed since the proposal was created, acceptance stops rather than overwriting those edits. An unavailable account, protected-state failure, or failed save also prevents acceptance. Changing executable steps does not inherit permission to run automatically. If the server saved a change but the local save could not finish, Plainwork tells you to check sync before retrying.
The local qualification harness uses scripted choices. Its success does not establish live-model reliability or compatibility with your website.