BrowserSkill lets agents reuse control across targeted browser actions BrowserSkill lets agents reuse control across targeted browser actions

A different default for shared control

New unconfigured sessions use a target-based policy: completed actions and additional reads can retain the same control context. Human intervention or navigation revokes that context. Scripts, untargeted keystrokes and visual actions still need an observation receipt and stricter freshness checks. Deploying the new behavior requires updating the command-line client, its running daemon, the extension and the DeepSeek Harness plugin together. Extension-store review can delay the browser component. A successful connection between mixed versions does not establish support for the new policy.

A node is not a business record

The cooperation guide distinguishes an element’s identity from its meaning. A virtualized table can reuse the same row for a different record; the same button can change from Save to Delete. Callers can attach expected text, values, checked states, attributes or existence to an action. Conditions use literal comparisons, without pattern matching or whitespace normalization. Selectors search the main document; references can address elements inside frames or shadow roots. The parser rejects unknown fields and values of the wrong type. Target names are capped at 1,024 Unicode code points; attribute names at 256. A tool receipt confirms the browser operation; application evidence establishes whether the business task succeeded. The extension implements these checks with fixed, read-only probes. Supplied text stays data rather than executable code, and mismatch diagnostics redact sensitive input values.

Coordination also observes human activity

BrowserSkill’s privacy policy explains that shared control observes page changes and supported manual activity even when debugging, audit and video recording are off. That observation supports handover within controlled task tabs; it does not start those optional recording features. The extension normally sends automation results to a local daemon, with an explicitly paired remote gateway available. It does not independently call an AI provider. The chosen agent or gateway can process or retain returned evidence under its own policies. Explicitly saved observation files contain the complete response before display filtering, so a shortened view does not remove content from the saved file.

Failure handling preserves the action’s history

An unknown outcome requires checking application records before retrying, because input may already have taken effect. Waiting for human control to end cannot repair a changed price or a missing element. Completed operations retain their receipts through ordinary page changes. After navigation, the next action needs a new synchronization. These distinctions separate permission to act, evidence used to choose an action and evidence of its result.