browser

# Browser Automation (Browserbase Remote) Drive Browserbase cloud browser sessions with the browse CLI. This skill is remote-only: every session runs in Browserbase's cloud with Identity, Verified browsers, automatic CAPTCHA solving, residential proxies, and persistent contexts. For local browser automation - localhost, dev flows, your own Chrome profile - use the `agent-browser` skill instead. ## When to Escalate Here This is the documented escalation path from `agent-browser`. Switch a run to a Browserbase session when the local browser hits: - CAPTCHAs: reCAPTCHA, hCaptcha, Turnstile - Bot-detection pages: "Checking your browser...", Cloudflare interstitials - HTTP 403/429, or empty pages on sites that should have content - Geo blocks that need residential proxies (201 countries, geo-targeting) - Sites that require a Verified browser via Browserbase Identity - Auth that must persist across sessions in the cloud (Browserbase contexts) - The user asks for it Don't escalate for simple sites (docs, wikis, public APIs) or localhost - stay on `agent-browser`. ## Setup check Before running any browser commands, verify the CLI is available: ```bash which browse || npm install -g @browserbasehq/browse-cli ``` **Warning**: the bare `browse` package on the npm registry is a different CLI. Always install `@browserbasehq/browse-cli`; it provides the `browse` binary. Remote sessions need credentials from https://browserbase.com/settings: ```bash export BROWSERBASE_API_KEY="bb...