Enable local preview access
- Start your preview server in the intended workspace and verify its local URL in a Browser panel.
- Open Settings → Browser.
- Enable Coding agent browser tools, then save settings.
- Return to the Code task and specify the local page and the interaction you want tested.
- Inspect the agent’s browser activity and answer any action-approval request.
The feature is off by default. The tools target loopback/local-preview pages rather than arbitrary remote sites. Availability also depends on how the selected harness receives browser tools; a visible manual Browser panel does not establish that every harness has the same tool connection.
Know which actions ask
The tool policy includes both inspection and actions. Local ephemeral actions can proceed without a separate approval. Persistent mutations and more consequential actions require approval: form submissions escalate, uploads are treated as irreversible, and external-navigation, download, or irreversible-looking controls can escalate too.
Do not assume all browser tools are read-only or that every click always asks first. Review the requested operation and any workspace file involved in an upload. An approval for one operation is not a promise that all later actions are permitted.
Recover blocked access
If a remote page is refused, use an authorized local preview for agent interaction; do not attempt to bypass the local boundary by relabeling a remote URL. If the local page fails, confirm the server is running, its port, and the actual URL. Check the toggle and selected harness’s tool availability.
For manual browsing and profile resets, use Browser. For missing tools or diagnostics, see Tools and workspace recovery.