OpenClaw Browser Batches Now Stop at Navigation—and Callers Must Read the Abort Signal

OpenClaw has changed the browser batch contract on main: when an action navigates the main frame or closes the page, the remaining actions are skipped and the result includes structured aborted metadata. Callers must re-snapshot before continuing.

That is safer than applying old element references to a new document. It is also an integration change: the actions that ran can all report success while requested tail actions did not run. Programmatic consumers that inspect only the existing results array can mistake partial execution for completion.

The operator decision

Why the old behavior was dangerous

Browser snapshot references belong to a document. In the old batch path, an early click or form submission could replace that document, while later actions continued resolving similarly named references on the new page. The batch could therefore perform the wrong action rather than fail obviously.

PR #113749 stops the batch after a main-frame navigation or page close. The response records why it stopped, after which action, the current URL and how many actions were skipped.

The distinction matters:

• results describes actions that actually ran;
• aborted describes requested actions that did not run; and
• abort is deliberately represented as a state transition, not as a failed executed action.

The maintainer explicitly retained that additive contract after review raised compatibility concerns. Existing callers therefore need an explicit aborted check; waiting for a nonzero exit or a failed result entry is insufficient.

The safe automation loop

A robust caller should now follow this pattern:

1. take an interactive snapshot and retain the current page identity;
2. batch only actions that are safe within that document;
3. inspect both per-action results and top-level abort metadata;
4. if navigation or close aborts the tail, discard old references;
5. take a fresh snapshot of the resulting page; and
6. decide what to do next from the new state rather than blindly replaying skipped actions.

Do not automatically rerun the skipped tail. The first action may have submitted an order, changed account state or moved into a different workflow. Recovery requires re-observation, not repetition.

Snapshot deltas reduce the re-observation cost

The same merge marks newly appeared reference-bearing elements with [new] across compatible consecutive snapshots and reports a newElements count. This is intended to surface autocomplete suggestions, dialogs, validation errors and other in-place changes without asking the model to mentally compare two complete trees.

The baseline is process-local and bounded. Navigation and tab closure reset it so a new document is not presented as entirely new. Same-URL single-page-app mutations are intentionally outside the navigation guard, making the delta markers and explicit state checks especially important on SPAs.

The Browser tool also gains a declared output schema covering snapshots, tabs, status, actions and batch-abort results. For code-mode consumers, that removes one discovery round trip—but only after the local tool catalogue or generated bindings have picked up the new schema.

Evidence and limits

Upstream reports 1,980 browser tests passing across 160 files, with one skip, plus changed-surface checks. The pull request also includes a redacted live transcript in which the first of three clicks navigates, two tail actions are skipped, a fresh snapshot produces document-scoped references and a follow-up click reaches the intended page.

Its 24-run fixture comparison moved from 19 successful runs on baseline to 20 on the branch, which the author correctly describes as statistically flat at that sample size. Delta markers appeared in 11 branch events; the batch guard did not trigger naturally in those model runs and was exercised separately. OpenClaw Academy reviewed the merged source record but did not run the unreleased browser build.

Bottom line

Stopping at document replacement is the right safety default. The footgun moves from “stale references can hit the wrong element” to “legacy callers may overlook that the tail was skipped.”

Before adopting a containing release, update every batch consumer to read aborted, throw away pre-navigation references and re-snapshot before deciding whether any skipped work is still appropriate.