browserlisted

# Browser Automation Automate browser interactions using the browse CLI with Claude. ## Setup check Before running any browser commands, verify the CLI is available: ```bash which browse || npm install -g browse ``` ## Environment Selection (Local vs Remote) The CLI supports explicit per-command environment flags. If you do nothing, the next session defaults to Browserbase when `BROWSERBASE_API_KEY` is set and to local otherwise. ### Local mode - `browse open <url> --local` starts a clean isolated local browser - `browse open <url> --auto-connect` attaches to an already-running debuggable Chrome; use `--local` when no debuggable Chrome is available - `browse open <url> --cdp <port|url>` attaches to a specific CDP target - Best for: development, localhost, trusted sites, and reproducible runs ### Remote mode (Browserbase) - `browse open <url> --remote` starts a Browserbase session - Without a local flag, Browserbase is also the default when `BROWSERBASE_API_KEY` is set - Provides: Browserbase Identity, Verified browsers, automatic CAPTCHA solving, residential proxies, session persistence - **Use remote mode when:** the target site has bot detection, CAPTCHAs, IP rate limiting, Cloudflare protection, or requires geo-specific access - Get credentials at https://browserbase.com/settings ### When to choose which - **Repeatable local testing / clean state**: `browse open <url> --local` - **Reuse your local login/cookies**: `browse open <url> --auto-connect` - **Simple brow