Browserbase Persist with captcha
by @jamesfincher
Create and manage persistent Browserbase cloud browser sessions with authentication persistence. Use when the user needs to automate browsers, maintain logged-in sessions across interactions, scrape authenticated pages, or manage cloud browser instances. Handles session creation, context-based auth persistence, keep-alive reconnection, captcha solving, session recording, screenshots, and session cleanup.
clawhub install browserbaseπ About This Skill
name: browserbase-sessions description: Create and manage persistent Browserbase cloud browser sessions with authentication persistence. Use when the user needs to automate browsers, maintain logged-in sessions across interactions, scrape authenticated pages, or manage cloud browser instances. Handles session creation, context-based auth persistence, keep-alive reconnection, captcha solving, session recording, screenshots, and session cleanup. license: MIT metadata: author: custom version: "2.0.0" openclaw: emoji: "π" requires: bins: ["python3"] anyBins: ["uv", "pip"] env: ["BROWSERBASE_API_KEY", "BROWSERBASE_PROJECT_ID"] primaryEnv: "BROWSERBASE_API_KEY"
Browserbase Sessions Skill
Manage persistent cloud browser sessions via Browserbase. This skill creates browser sessions that preserve authentication (cookies, local storage) across interactions, automatically solve CAPTCHAs, and record sessions for later review.
First-Time Setup
Step 1 β Get your Browserbase credentials
1. Sign up at browserbase.com if you haven't already.
2. Go to Settings β API Keys and copy your API key (starts with bb_live_).
3. Go to Settings β Project and copy your Project ID (a UUID).
Step 2 β Install dependencies
cd {baseDir}/scripts && pip install -r requirements.txt
playwright install chromium
Or with uv:
cd {baseDir}/scripts && uv pip install -r requirements.txt
uv run playwright install chromium
Step 3 β Set environment variables
export BROWSERBASE_API_KEY="bb_live_your_key_here"
export BROWSERBASE_PROJECT_ID="your-project-uuid-here"
Or configure via OpenClaw's skills.entries.browserbase-sessions.env in ~/.openclaw/openclaw.json.
Step 4 β Run the setup test
This validates everything end-to-end (credentials, SDK, Playwright, API connection, and a live smoke test):
python3 {baseDir}/scripts/browserbase_manager.py setup
You should see "status": "success" with all steps passing. If any step fails, the error message tells you exactly what to fix.
Defaults
Every session is created with these defaults to support research workflows:
--no-solve-captchas.--no-record.--persist to stay logged in across sessions.Available Commands
All commands are run via the manager script:
python3 {baseDir}/scripts/browserbase_manager.py [options]
Setup & Validation
Run the full setup test:
python3 {baseDir}/scripts/browserbase_manager.py setup
Context Management (for authentication persistence)
Create a named context to store login state:
python3 {baseDir}/scripts/browserbase_manager.py create-context --name github
List all saved contexts:
python3 {baseDir}/scripts/browserbase_manager.py list-contexts
Delete a context (by name or ID):
python3 {baseDir}/scripts/browserbase_manager.py delete-context --context-id github
Session Lifecycle
Create a new session (captcha solving and recording enabled by default):
# Basic session
python3 {baseDir}/scripts/browserbase_manager.py create-sessionSession with saved context (persist=true saves cookies on close)
python3 {baseDir}/scripts/browserbase_manager.py create-session --context-id github --persistKeep-alive session for long research (survives disconnections)
python3 {baseDir}/scripts/browserbase_manager.py create-session --context-id github --persist --keep-alive --timeout 3600Full options
python3 {baseDir}/scripts/browserbase_manager.py create-session \
--context-id github \
--persist \
--keep-alive \
--timeout 3600 \
--region us-west-2 \
--proxy \
--block-ads \
--viewport-width 1280 \
--viewport-height 720
List all sessions:
python3 {baseDir}/scripts/browserbase_manager.py list-sessions
python3 {baseDir}/scripts/browserbase_manager.py list-sessions --status RUNNING
Get session details:
python3 {baseDir}/scripts/browserbase_manager.py get-session --session-id
Terminate a session:
python3 {baseDir}/scripts/browserbase_manager.py terminate-session --session-id
Browser Automation
Navigate to a URL:
# Navigate and get page title
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://example.com"Navigate and extract text
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://example.com" --extract-textNavigate and save screenshot
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://example.com" --screenshot /tmp/page.pngNavigate and take full-page screenshot
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://example.com" --screenshot /tmp/full.png --full-page
Take a screenshot of the current page (without navigating):
python3 {baseDir}/scripts/browserbase_manager.py screenshot --session-id --output /tmp/current.png
python3 {baseDir}/scripts/browserbase_manager.py screenshot --session-id --output /tmp/full.png --full-page
Execute JavaScript:
python3 {baseDir}/scripts/browserbase_manager.py execute-js --session-id --code "document.title"
Get cookies:
python3 {baseDir}/scripts/browserbase_manager.py get-cookies --session-id
Recordings, Logs & Debug
Download a session recording video (session must be terminated first):
python3 {baseDir}/scripts/browserbase_manager.py get-recording --session-id --output /tmp/session.webm
Get session logs:
python3 {baseDir}/scripts/browserbase_manager.py get-logs --session-id
Get the live debug URL (for visual inspection of a running session):
python3 {baseDir}/scripts/browserbase_manager.py live-url --session-id
Common Workflows
Workflow 1: Multi-session research with persistent login
# 1. One-time: create a named context for the site
python3 {baseDir}/scripts/browserbase_manager.py create-context --name myapp2. Start a research session (captchas auto-solved, recording on)
python3 {baseDir}/scripts/browserbase_manager.py create-session --context-id myapp --persist --keep-alive --timeout 36003. Navigate to login β captchas solved automatically
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://myapp.com/login"
Use execute-js to fill forms and submit
4. Do research, take screenshots
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://myapp.com/dashboard" --extract-text
python3 {baseDir}/scripts/browserbase_manager.py screenshot --session-id --output /tmp/dashboard.png5. Terminate (cookies saved to context)
python3 {baseDir}/scripts/browserbase_manager.py terminate-session --session-id 6. Download recording to share
python3 {baseDir}/scripts/browserbase_manager.py get-recording --session-id --output /tmp/research.webm7. Next day: new session, already logged in!
python3 {baseDir}/scripts/browserbase_manager.py create-session --context-id myapp --persist --keep-alive --timeout 3600
Workflow 2: Screenshot documentation
python3 {baseDir}/scripts/browserbase_manager.py create-session
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://docs.example.com" --screenshot /tmp/docs_home.png
python3 {baseDir}/scripts/browserbase_manager.py navigate --session-id --url "https://docs.example.com/api" --screenshot /tmp/docs_api.png --full-page
python3 {baseDir}/scripts/browserbase_manager.py terminate-session --session-id
Workflow 3: Record and share a walkthrough
# Session recording is ON by default
python3 {baseDir}/scripts/browserbase_manager.py create-session --context-id myapp --persist
... do your walkthrough (navigate, click, etc.) ...
python3 {baseDir}/scripts/browserbase_manager.py terminate-session --session-id
Download the video
python3 {baseDir}/scripts/browserbase_manager.py get-recording --session-id --output /tmp/walkthrough.webm
Important Notes
--no-solve-captchas to disable.get-recording after termination. Use --no-record to disable.terminate-session --persist before creating a new session with the same context.--name with create-context to save friendly names (e.g. github, slack). Use the name anywhere a context ID is expected.Error Handling
All commands return JSON output. On error, the output includes an "error" key. Common errors:
APIConnectionError: Browserbase API unreachableRateLimitError: Too many concurrent sessions for your planAPIStatusError: Invalid parameters or authentication failureBROWSERBASE_API_KEY and BROWSERBASE_PROJECT_IDReference
For full API details, read {baseDir}/references/api-quick-ref.md.