Browser
BrowserbaseOfficialPublished by Browserbase
- Skill
- Tool integration
- Automation and integrations
- MIT
- Low risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The browser skill provides a command-line interface for controlling web browsers to perform tasks such as navigation, data extraction, form filling, and interaction with web applications. It supports both local browser instances and remote sessions via Browserbase, offering features like automatic CAPTCHA solving, residential proxies, and session persistence. This tool is designed to help AI agents navigate the web, interact with complex or protected sites, and retrieve structured page information efficiently.
What it does
- Navigates to websites and manages browser sessions.
- Extracts structured data, HTML, or markdown from web pages.
- Interacts with web elements like buttons, forms, and dropdowns.
- Supports remote browsing with CAPTCHA solving and residential proxies.
- Captures visual screenshots or accessibility snapshots for page state analysis.
- Streams Chrome DevTools Protocol (CDP) events for advanced debugging.
When to use it
- When you need to scrape data from websites or interact with web-based forms.
- When navigating sites protected by bot detection, CAPTCHAs, or IP rate limiting.
- When you need to perform automated testing or visual verification of a web page.
- When you need to reuse existing local browser cookies or session state.
- When you need to monitor network or console events via CDP.
Advantages
- Flexible execution modes (local, remote, or attached to existing debuggable Chrome).
- Efficient page state retrieval using accessibility snapshots instead of heavy screenshots.
- Built-in support for bypassing common web protections like Cloudflare and CAPTCHAs.
- Provides granular control over browser interactions through natural language commands.
- Supports session persistence and geo-specific access via residential proxies.
Usage examples
- “Browse to https://example.com and extract the main content as markdown.”
- The agent will open the URL, retrieve the page content, and return it formatted as markdown.
- “Fill out the login form on the current page with my credentials and click submit.”
- The agent will identify the form fields, input the provided data, and trigger the submit action.
- “Take a screenshot of the current page to debug a layout issue.”
- The agent will capture a visual image of the page and save it to the specified path.
- “Use remote mode to access a site that is blocking my local IP.”
- The agent will initiate a Browserbase session using residential proxies to bypass the IP block.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/browserbase/browser/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip browser.zip -d .agents/skills
Documentation by Browserbase
Browser Automation
Automate browser interactions using the browse CLI with Claude.
Setup check
Before running any browser commands, verify the CLI is available:
which browse || npm install -g browseEnvironment 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> --localstarts a clean isolated local browserbrowse open <url> --auto-connectattaches to an already-running debuggable Chrome; use--localwhen no debuggable Chrome is availablebrowse open <url> --cdp <port|url>attaches to a specific CDP targetBest for: development, localhost, trusted sites, and reproducible runs
Remote mode (Browserbase)
browse open <url> --remotestarts a Browserbase sessionWithout a local flag, Browserbase is also the default when
BROWSERBASE_API_KEYis setProvides: 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> --localReuse your local login/cookies:
browse open <url> --auto-connectSimple browsing (docs, wikis, public APIs): local mode is fine
Protected sites (login walls, CAPTCHAs, anti-scraping): use remote mode
If local mode fails with bot detection or access denied: switch to remote mode
Commands
Most driver commands work across local, remote, and CDP sessions after the daemon starts.
Navigation
browse open <url> # Go to URL
browse open <url> --local # Go to URL in a clean local browser
browse open <url> --remote # Go to URL in a Browserbase session
browse reload # Reload current page
browse back # Go back in history
browse forward # Go forward in historyPage state (prefer snapshot over screenshot)
browse snapshot # Get accessibility tree with element refs (fast, structured)
browse screenshot --path <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 markdown [selector] # Get page content as markdown (defaults to body)
browse get value <selector> # Get form field valueUse 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).
Interaction
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; add --press-enter if Enter is needed
browse select <selector> <values...> # Select dropdown option(s)
browse upload <selector> <files...> # Upload file(s) to <input type="file">
browse press <key> # Press key (Enter, Tab, Escape, Cmd+A, etc.)
browse mouse drag <fromX> <fromY> <toX> <toY> # Drag from one point to another
browse mouse 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, timeoutCDP event tailing
browse cdp <url|port> # Stream CDP events as NDJSON from any target
browse cdp 9222 # Attach to local Chrome on port 9222
browse cdp ws://localhost:9222/devtools/browser/... # Full WebSocket URL
browse cdp <url> --domain Network # Only Network events
browse cdp <url> --domain Network --domain Console # Multiple domains
browse cdp <url> --pretty # Human-readable output
browse cdp <url> > events.jsonl # Pipe to file
browse cdp <url> | jq '.method' # Filter with jqThe cdp command connects directly to any Chrome DevTools Protocol target and streams events. It does not use the daemon — it's a standalone, long-running process. Press Ctrl+C to stop. Default domains: Network, Console, Runtime, Log, Page.
Session management
browse stop # Stop the browser daemon
browse status # Check daemon status and resolved mode
browse tab list # List all open tabs
browse tab switch <index-or-target-id> # Switch to tab by index or target ID
browse tab close [index-or-target-id] # Close tabTypical workflow
If the environment matters, put --local, --remote, --auto-connect, or --cdp <port|url> on the first browser command.
browse open <url> --localorbrowse open <url> --remote— 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 workedRepeat 3-4 as needed
browse stop— close the browser when done
Quick Example
browse 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 stopMode Comparison
| Feature | Local | Browserbase |
|---|---|---|
| Speed | Faster | Slightly slower |
| Setup | Chrome required | API key required |
| Reuse existing local cookies | With browse open <url> --auto-connect | N/A |
| Verified browser | No | Yes (Browserbase Verified browser via Identity) |
| CAPTCHA solving | No | Yes (automatic reCAPTCHA/hCaptcha) |
| Residential proxies | No | Yes (201 countries, geo-targeting) |
| Session persistence | No | Yes (cookies/auth persist via contexts) |
| Best for | Development/simple pages | Protected sites, Browserbase Identity + Verified access, production scraping |
Best Practices
Choose the local strategy deliberately: use
browse open <url> --localfor clean state,browse open <url> --auto-connectfor existing local credentials, andbrowse open <url> --remotefor protected sitesAlways
browse openfirst before interactingUse
browse snapshotto check page state — it's fast and gives you element refsOnly screenshot when visual context is needed (layout checks, images, debugging)
Use refs from snapshot to click/interact — e.g.,
browse click @0-5browse stopwhen done to clean up the browser session and clear the env override
Troubleshooting
"No active page": Run
browse stop, then checkbrowse status. If it still says running, kill the zombie daemon withpkill -f "browse.*daemon", then retrybrowse openChrome not found: Install Chrome, use
browse open <url> --auto-connectif you already have a debuggable Chrome running, or switch tobrowse open <url> --remoteAction fails: Run
browse snapshotto see available elements and their refsBrowserbase fails: Verify API key is set
Switching to Remote Mode
Switch 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 open <url> --local # clean isolated local browser
browse open <url> --auto-connect # attach to existing debuggable Chrome
browse open <url> --remote # Browserbase sessionMode flags are applied when a session starts. After browse stop, the next start falls back to env-var-based auto detection. Use browse status to inspect the resolved mode and target while the daemon is running.
For detailed examples, see EXAMPLES.md. For API reference, see REFERENCE.md.
Files
- ATTRIBUTION.mdAdded by AutoGineer850 B
- EXAMPLES.md6.2 KiB
- LICENSE.txt1.0 KiB
- REFERENCE.md15.2 KiB
- SKILL.md9.5 KiB
REFERENCE.md
Browser Automation CLI Reference
Technical reference for the browse CLI tool.
Table of Contents
Architecture
Command Reference
Navigation
Page State
Interaction
Session Management
JavaScript Evaluation
Viewport
Network Capture
Configuration
Global Flags
Environment Variables
Error Messages
Architecture
The browse CLI is a daemon-based command-line tool:
Daemon process: A background process manages the browser instance. Auto-starts on the first command (e.g.,
browse open), persists across commands, and stops withbrowse stop.Local mode:
browse open <url> --locallaunches a clean isolated local browser. It is the default whenBROWSERBASE_API_KEYis unset. Usebrowse open <url> --auto-connectto attach to an existing debuggable Chrome, orbrowse open <url> --cdp <port|url>to attach to a specific CDP target.Remote mode (Browserbase): Connects to a Browserbase cloud browser session when
BROWSERBASE_API_KEYis set.Accessibility-first: Use
browse snapshotto get the page's accessibility tree with element refs, then interact using those refs.
Command Reference
Navigation
open <url>
Navigate to a URL. Auto-starts the daemon if not running.
browse open https://example.com
browse open https://example.com --wait networkidle # wait for all network requests to finish (useful for SPAs)
browse open https://example.com --wait domcontentloadedThe --wait flag controls when navigation is considered complete. Values: load (default), domcontentloaded, networkidle. Use networkidle for JavaScript-heavy pages that fetch data after initial load.
Context persistence (remote mode only)
Create a Browserbase session with browse cloud sessions create --context-id <id>, then attach to its CDP endpoint with browse open <url> --cdp <connectUrl>. Add --persist to the cloud session if state changes should save back to the context.
SESSION_JSON="$(browse cloud sessions create --context-id ctx_abc123 --persist --keep-alive)"
SESSION_ID="$(echo "$SESSION_JSON" | jq -r .id)"
CONNECT_URL="$(echo "$SESSION_JSON" | jq -r .connectUrl)"
browse open https://example.com --cdp "$CONNECT_URL"
# ...interact with the page...
browse stop
browse cloud sessions update "$SESSION_ID" --status REQUEST_RELEASE--context-id <id>— Browserbase context ID to load when creating the cloud session.--persist— Save cookies/storage changes back to the context when the Browserbase session is released. Requires--context-id.--keep-alive— Keep the Browserbase session alive while the local browse daemon attaches and detaches.After
browse open ... --cdp "$CONNECT_URL", follow-up commands in that session do not repeat--cdp; the daemon remembers the attached target.
reload
Reload the current page.
browse reloadback / forward
Navigate browser history.
browse back
browse forwardPage State
snapshot
Get the accessibility tree with interactive element refs. This is the primary way to understand page structure.
browse snapshot
browse snapshot --compact # tree only, no ref mapsReturns a text representation of the page with refs like @0-5 that can be passed to click. Use --compact for shorter output when you only need the tree.
screenshot [path]
Take a visual screenshot. Slower than snapshot and uses vision tokens.
browse screenshot # print base64 JSON
browse screenshot --path ./capture.png # custom path
browse screenshot --full-page # capture entire scrollable pageget <property> [selector]
Get page properties. Available properties: url, title, text, html, markdown, value, box, visible, checked.
browse get url # current URL
browse get title # page title
browse get text "body" # all visible text (selector required)
browse get text ".product-info" # text within a CSS selector
browse get html "#main" # inner HTML of an element
browse get markdown # full page body as markdown
browse get markdown ".article" # specific element as markdown
browse get value "#email-input" # value of a form field
browse get box "#header" # bounding box (centroid coordinates)
browse get visible ".modal" # check if element is visible
browse get checked "#agree" # check if checkbox/radio is checkedNote: get text and get html require a selector argument — use "body" for full page content. get markdown defaults to body when no selector is given.
Tip: Prefer get markdown over get text or get html when you need readable page content for analysis — it preserves links, headings, and structure without HTML noise.
refs
Show the cached ref map from the last browse snapshot. Useful for looking up element refs without re-running a full snapshot.
browse refsInteraction
click <ref>
Click an element by its ref from browse snapshot output.
browse click @0-5 # click element with ref 0-5click_xy <x> <y>
Click at exact viewport coordinates.
browse click_xy 500 300hover <x> <y>
Hover at viewport coordinates.
browse hover 500 300type <text>
Type text into the currently focused element.
browse type "Hello, world!"
browse type "slow typing" --delay 100 # 100ms between keystrokes
browse type "human-like" --mistakes # simulate human typing with typosfill <selector> <value>
Fill an input element matching a CSS selector. Add --press-enter when Enter is needed.
browse fill "#search" "browser automation"
browse fill "input[name=email]" "[email protected]"
browse fill "#search" "query" --press-enter # fill and press Enterselect <selector> <values...>
Select option(s) from a dropdown.
browse select "#country" "United States"
browse select "#tags" "javascript" "typescript" # multi-selectupload <selector> <files...>
Upload file(s) to an <input type="file"> element. Works with both local and remote Browserbase sessions (remote uses base64 injection). Supports ref-based selectors from snapshot.
browse upload "#fileUpload" ./document.pdf # single file
browse upload @0-5 ./photo.png # using ref from snapshot
browse upload "#files" ./a.png ./b.png # multiple filespress <key>
Press a keyboard key or key combination.
browse press Enter
browse press Tab
browse press Escape
browse press Cmd+A # select all (Mac)
browse press Ctrl+C # copy (Linux/Windows)mouse scroll <x> <y> <deltaX> <deltaY>
Scroll at a given position by a given amount.
browse mouse scroll 500 300 0 -300 # scroll up at (500, 300)
browse mouse scroll 500 300 0 500 # scroll downmouse drag <fromX> <fromY> <toX> <toY>
Drag from one viewport coordinate to another.
browse mouse drag 80 80 310 100 # drag with default 10 steps
browse mouse drag 80 80 310 100 --steps 20 # more intermediate steps
browse mouse drag 80 80 310 100 --delay 50 # 50ms between steps
browse mouse drag 80 80 310 100 --button right # use right mouse button
browse mouse drag 80 80 310 100 --return-xpath # return source/target XPathshighlight <selector>
Highlight an element on the page for visual debugging.
browse highlight "#submit-btn" # highlight for 2 seconds (default)
browse highlight ".nav" -d 5000 # highlight for 5 secondsis <check> <selector>
Check element state. Available checks: visible, checked.
browse is visible ".modal" # returns { visible: true/false }
browse is checked "#agree" # returns { checked: true/false }wait <type> [arg]
Wait for a condition.
browse wait load # wait for page load
browse wait "selector" ".results" # wait for element to appear
browse wait timeout 3000 # wait 3 secondsSession Management
start
Start the browser daemon manually. Usually not needed — the daemon auto-starts on first command.
browse startstop
Stop the browser daemon and close the browser.
browse stop
browse stop --force # force kill if daemon is unresponsivestatus
Check whether the daemon is running, its connection details, and current environment.
browse statusStarting sessions with a mode flag
Choose the browser target on the command that starts the session:
browse open https://example.com --local
browse open https://example.com --local --headed
browse open https://example.com --auto-connect
browse open https://example.com --cdp 9222
browse open https://example.com --cdp ws://localhost:9222/devtools/browser/...
browse open https://example.com --remotebrowse statusshows the resolved mode and active target once the daemon is running.browse stopcloses the current daemon session; the nextbrowse openchooses mode from its flags or environment.
tab new [url]
Create a new tab, optionally navigating to a URL.
browse tab new # open blank tab
browse tab new https://example.com # open tab with URLtab list
List all open tabs.
browse tab listtab switch <index-or-target-id>
Switch to a tab by its index or target ID (from browse tab list).
browse tab switch 1tab close [index-or-target-id]
Close a tab. Closes current tab if no index given. The CLI refuses to close the last remaining tab.
browse tab close # close current tab
browse tab close 2 # close tab at index 2JavaScript Evaluation
eval <expression>
Evaluate JavaScript in the page context.
browse eval "document.title"
browse eval "document.querySelectorAll('a').length"Viewport
viewport <width> <height>
Set the browser viewport size.
browse viewport 1920 1080Network Capture
Capture network requests to the filesystem for inspection.
network on
Enable network request capture. Creates a temp directory where requests and responses are saved as JSON files.
browse network onnetwork off
Disable network capture.
browse network offnetwork path
Show the capture directory path.
browse network pathnetwork clear
Clear all captured requests.
browse network clearCDP Event Tailing
cdp <url|port>
Attach to any Chrome DevTools Protocol target and stream events as NDJSON (one JSON object per line). This command bypasses the daemon entirely — it opens a direct WebSocket connection and runs until interrupted.
browse cdp 9222 # bare port — auto-discovers via /json/version
browse cdp ws://127.0.0.1:9222/devtools/browser/... # full WebSocket URL
browse cdp wss://connect.browserbase.com/debug/... # remote Browserbase debug URLOptions:
| Flag | Description |
|---|---|
--domain <domains...> | CDP domains to enable (repeatable). Default: Network, Console, Runtime, Log, Page |
--pretty | Human-readable output instead of JSON. Auto-enabled for TTY |
Default domains: Network, Console, Runtime, Log, Page. To capture only specific domains:
browse cdp 9222 --domain Network # network events only
browse cdp 9222 --domain Network --domain Console # network + consolePiping and filtering:
browse cdp 9222 > events.jsonl # save to file
browse cdp 9222 | jq '.method' # extract method names
browse cdp 9222 | jq 'select(.method == "Network.requestWillBeSent") | .params.request.url'Pretty output shows compact one-line summaries:
[Target.attachedToTarget] [page] https://example.com
[Network.requestWillBeSent] GET https://example.com/api/data
[Network.responseReceived] 200 https://example.com/api/data
[Runtime.consoleAPICalled] [log] Hello world
[Page.frameNavigated] https://example.com/aboutWith Browserbase sessions: Use bb sessions debug <session-id> to get the wsUrl, then pass it to browse cdp:
# Get the debug WebSocket URL
bb sessions debug <session-id>
# Copy the wsUrl field and pass it to browse cdp
browse cdp wss://connect.browserbase.com/debug/<session-id>/devtools/browser/...Configuration
Common Flags
--session <name>
Run commands against a named session, enabling multiple concurrent browsers.
browse open https://a.com --session work
browse open https://b.com --session personalContext flags such as --context-id and --persist live on browse cloud sessions create; attach to the resulting connectUrl with browse open ... --cdp <connectUrl>.
Environment Variables
| Variable | Required | Description |
|---|---|---|
BROWSE_SESSION | No | Default session name (alternative to --session) |
BROWSERBASE_API_KEY | For remote mode | API key from https://browserbase.com/settings; makes Browserbase the default desired mode when no override is set |
BROWSERBASE_PROJECT_ID | No | Passed through to Browserbase when set |
Without an override, setting BROWSERBASE_API_KEY makes Browserbase the default desired mode. Otherwise the default desired mode is local. Use --local, --remote, --auto-connect, or --cdp <port|url> on browse open when you need an explicit target.
Setting credentials
export BROWSERBASE_API_KEY="bb_live_..."Get these values from https://browserbase.com/settings.
Error Messages
"No active page"
The daemon is running but has no page open.
Fix: Run
browse open <url>. If the issue persists, runbrowse stopand retry. For zombie daemons:pkill -f "browse.*daemon".
"Chrome not found" / "Could not find local Chrome installation"
Chrome/Chromium is not installed or not in a standard location.
Fix: Install Chrome, use
browse open <url> --auto-connectif you already have a debuggable Chrome running, or switch to remote withbrowse open <url> --remote(no local browser needed).
"Daemon not running"
No daemon process is active. Most commands auto-start the daemon, but
snapshot,click, etc. require an active session.Fix: Run
browse open <url>to start a session.
Element ref not found (e.g., "@0-5")
The ref from a previous snapshot is no longer valid (page changed).
Fix: Run
browse snapshotagain to get fresh refs.
Timeout errors
The page took too long to load or an element didn't appear.
Fix: Try
browse wait loadbefore interacting, or increase wait time.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools, Needs an API key, Needs Node.js
The author says: Requires the browse CLI (`npm install -g browse`). Remote Browserbase sessions need `BROWSERBASE_API_KEY`. Local mode uses Chrome/Chromium on your machine.
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Browserbase
- Publisher
- Browserbase (Official)
- Source
- browserbase/skills · skills/browser · commit 6811ca3
- Licence
- MIT License (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Browserbase.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download browser.zip