Browser
Browser tools let Anyy navigate pages, inspect content, interact with controls, and capture page evidence through a configured browser backend.
Recommended Setup
Open Dashboard → Tools → Browser. Choose a preset, review the generated command and endpoint, start the required browser bridge, then select Check connection before enabling it.
For the shortest local CLI path:
anyy browser connect --browser chrome
The local path uses an isolated browser profile and asks for explicit confirmation. Add --headless when you do not need a visible window, or --yes only after reviewing what the command will launch.
Supported Connection Paths
| Path | Use it when |
|---|---|
| Isolated local browser | You want the recommended private Anyy-controlled browser session |
| Playwright MCP endpoint | A supported browser bridge already runs locally or on a trusted host |
| CDP endpoint | You deliberately manage a Chromium debugging endpoint |
agent-browser compatibility backend | You already operate its fixed stdio MCP mode |
Advanced CLI examples:
anyy browser connect --url http://127.0.0.1:8931/mcp
anyy browser connect --backend agent-browser --args mcp
Do not expose an unauthenticated browser-control endpoint to an untrusted network.
Check and Diagnose
anyy browser status
anyy browser doctor
Status reports the configured backend, endpoint, connection, and whether the browser toolset is available. Doctor distinguishes configuration errors, missing bridge processes, unreachable endpoints, and tool discovery failures.
Use Browser Tools
After setup, ask Anyy for an explicit browser task:
Open the release notes page, list the breaking changes, and cite the sections you used.
Anyy can use only the actions exposed by the connected backend. Authentication state belongs to that isolated profile or external backend; it is not copied automatically from your normal browser.
Submitting forms, sending messages, purchasing, deleting, or publishing can affect other people and systems. Keep approvals enabled and review the target, account, and final action.
Disconnect or Disable
anyy browser disconnect
anyy browser disable
Disconnect stops the active connection. Disable also removes browser capability from the Profile's default toolsets. Dashboard provides the matching stop and disable controls.
Troubleshooting
| Symptom | Check |
|---|---|
| Browser tool is unavailable | Confirm Browser is enabled in Dashboard and run anyy browser status |
| Endpoint cannot be reached | Start the bridge and verify its exact URL from the same host as Gateway |
| Wrong browser/profile opens | Review the selected browser and profile directory in the preset |
| A logged-in site appears logged out | Authenticate inside the isolated Profile; normal-browser cookies are not assumed |
| Remote setup works only locally | Fix bind address, routing, and authentication before exposing it |