Browserbase
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from w...
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from w...
Real data. Real impact.
Emerging
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
Automate browser interactions using the browse CLI with Claude.
Before running any browser commands, verify the CLI is available:
which browse || npm install -g @browserbasehq/browse-cli
The CLI automatically selects between local and remote browser environments based on available configuration:
BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID are setAll commands work identically in both modes. The daemon auto-starts on first command.
browse open <url> # Go to URL (aliases: goto) browse reload # Reload current page browse back # Go back in history browse forward # Go forward in history
browse snapshot # Get accessibility tree with element refs (fast, structured) browse screenshot [path] # Take visual screenshot (slow, uses vision tokens) browse get url # Get current URL browse get title # Get page title browse get text <selector> # Get text content (use "body" for all text) browse get html <selector> # Get HTML content of element browse get value <selector> # Get form field value
Use
browse snapshot as your default for understanding page state — it returns the accessibility tree with element refs you can use to interact. Only use browse screenshot when you need visual context (layout, images, debugging).
browse click <ref> # Click element by ref from snapshot (e.g., @0-5) browse type <text> # Type text into focused element browse fill <selector> <value> # Fill input and press Enter browse select <selector> <values...> # Select dropdown option(s) browse press <key> # Press key (Enter, Tab, Escape, Cmd+A, etc.) browse drag <fromX> <fromY> <toX> <toY> # Drag from one point to another browse scroll <x> <y> <deltaX> <deltaY> # Scroll at coordinates browse highlight <selector> # Highlight element on page browse is visible <selector> # Check if element is visible browse is checked <selector> # Check if element is checked browse wait <type> [arg] # Wait for: load, selector, timeout
browse stop # Stop the browser daemon browse status # Check daemon status (includes env) browse env # Show current environment (local or remote) browse env local # Switch to local Chrome browse env remote # Switch to Browserbase (requires API keys) browse pages # List all open tabs browse tab_switch <index> # Switch to tab by index browse tab_close [index] # Close tab
browse open <url> — navigate to the pagebrowse snapshot — read the accessibility tree to understand page structure and get element refsbrowse click <ref> / browse type <text> / browse fill <selector> <value> — interact using refs from snapshotbrowse snapshot — confirm the action workedbrowse stop — close the browser when donebrowse open https://example.com browse snapshot # see page structure + element refs browse click @0-5 # click element with ref 0-5 browse get title browse stop
| Feature | Local | Browserbase |
|---|---|---|
| Speed | Faster | Slightly slower |
| Setup | Chrome required | API key required |
| Stealth mode | No | Yes (custom Chromium, anti-bot fingerprinting) |
| CAPTCHA solving | No | Yes (automatic reCAPTCHA/hCaptcha) |
| Residential proxies | No | Yes (201 countries, geo-targeting) |
| Session persistence | No | Yes (cookies/auth persist across sessions) |
| Best for | Development/simple pages | Protected sites, bot detection, production scraping |
browse open first before interactingbrowse snapshot to check page state — it's fast and gives you element refsbrowse click @0-5browse stop when done to clean up the browser sessionbrowse stop, then check browse status. If it still says running, kill the zombie daemon with pkill -f "browse.*daemon", then retry browse openbrowse env remotebrowse snapshot to see available elements and their refsSwitch to remote when you detect: CAPTCHAs (reCAPTCHA, hCaptcha, Turnstile), bot detection pages ("Checking your browser..."), HTTP 403/429, empty pages on sites that should have content, or the user asks for it.
Don't switch for simple sites (docs, wikis, public APIs, localhost).
browse env remote # switch to Browserbase browse env local # switch back to local Chrome
The switch is sticky until you run
browse stop or switch again.
For detailed examples, see EXAMPLES.md. For API reference, see REFERENCE.md.
No automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.