browserlisted

# Browser Autodev drives browsers two ways. **Pick the driver first — everything else follows from it.** ## Choose a driver **Use the built-in browser tools when `mcp__Claude_Browser__*` tools are available.** This is the default in the Claude Code desktop app and any session with the Browser pane. It needs no install, no daemon, and no Chromium download, and the user can watch the page as you drive it. **Fall back to the `agent-browser` CLI only when those tools are absent** — a plain terminal session — *and* `command -v agent-browser` succeeds. Read [references/agent-browser-cli.md](references/agent-browser-cli.md) for the full command set at that point, not before: it is a long reference and costs context you do not need on the built-in path. If neither is available, say so and stop. Do not `npm install -g agent-browser` without asking — it downloads a Chromium build. ## Built-in path Start the app, then drive it: | Goal | Tool | |------|------| | Start the project's dev server | `preview_start` with a `.claude/launch.json` entry | | Open a URL (no server needed) | `preview_start` with `{url}`, then `navigate` | | Read page structure + get refs | `read_page` — prefer this over screenshots for text and structure | | Read visible copy | `get_page_text` | | Click / type / scroll / hover | `computer` with a `ref_N` from `read_page`, or coordinates | | Fill a field reliably | `form_input` with a `ref_N` | | Find an element by description | `find` (after `read_page`) | |