From browserbase-cli
Syncs cookies from local Chrome to Browserbase persistent contexts for authenticated browsing with the browse CLI. Supports domain filtering, context refresh, stealth mode, and proxies.
npx claudepluginhub browserbase/skills --plugin browserbase-cliThis skill uses the workspace's default tool permissions.
Exports cookies from your local Chrome and saves them into a Browserbase **persistent context**. After syncing, use the `browse` CLI to open authenticated sessions with that context.
Controls existing Chrome browsers via DevTools Protocol using use_browser tool for multi-tab management, navigation, form automation, interactions, and content extraction. Use for authenticated sessions or when Playwright is unsuitable.
Automates browser tasks via CLI: navigate pages, extract data, fill forms, click buttons, take screenshots. Supports stealth remote sessions with CAPTCHA solving for protected sites.
Automates browser interactions for AI agents via Smooth CLI: navigate sites, fill forms, scrape data, test web apps, log in, and run natural language tasks.
Share bugs, ideas, or general feedback.
Exports cookies from your local Chrome and saves them into a Browserbase persistent context. After syncing, use the browse CLI to open authenticated sessions with that context.
Supports domain filtering (only sync cookies you need) and context reuse (refresh cookies without creating a new context).
chrome://flags/#allow-remote-debugging, enable it and restart the browser--remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug and set CDP_URL=ws://127.0.0.1:9222BROWSERBASE_API_KEYInstall dependencies before first use:
cd .claude/skills/cookie-sync && npm install
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs
Creates a persistent context with all your Chrome cookies. Outputs a context ID.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --domains google.com,github.com
Matches the domain and all subdomains (e.g. google.com matches accounts.google.com, mail.google.com, etc.)
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --context ctx_abc123
Re-injects fresh cookies into a previously created context. Use this when cookies have expired.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --stealth
Enables Browserbase's advanced stealth mode to reduce bot detection. Recommended for sites like Google that fingerprint browsers.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --proxy "San Francisco,CA,US"
Routes through a residential proxy in the specified location. Format: "City,ST,Country" (state is 2-letter code). Helps match your local IP's geolocation so auth cookies aren't rejected.
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --domains github.com,google.com --stealth --proxy "San Francisco,CA,US"
After syncing, use the browse CLI with the context ID:
browse open https://mail.google.com --context-id <ctx-id> --persist
The --persist flag saves any new cookies or state changes back to the context, keeping the session fresh for next time.
Full workflow example:
# Step 1: Sync cookies for Twitter
node .claude/skills/cookie-sync/scripts/cookie-sync.mjs --domains x.com,twitter.com
# Output: Context ID: ctx_abc123
# Step 2: Browse authenticated Twitter
browse open https://x.com/messages --context-id ctx_abc123 --persist
browse snapshot
browse screenshot
browse stop
Contexts persist across sessions, making them ideal for scheduled/recurring tasks:
browse open <url> --context-id <ctx-id> --persist — no local Chrome needed--context <ctx-id> to refreshchrome://flags/#allow-remote-debugging if your browser build exposes it, or launch with --remote-debugging-port=9222 and set CDP_URL=ws://127.0.0.1:9222--context <id> to refresh--stealth and/or --proxy with a location near you