{"name":"browserbase-cli","url":"https://skills.sh/browserbase/skills/browserbase-cli","install":"npx skills add browserbase/skills --skill browserbase-cli","sdk":"browserbase","key":"browserbase/browserbase-cli","description":"Use the Browserbase CLI (`browse`) for Browserbase Functions and platform API workflows. Use when the user asks to run `browse`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use the top-level `browse` driver commands (`browse open`, `browse get`, etc.) only when the user explicitly wants the CLI path.","hasContent":true,"content":"---\nname: browserbase-cli\ndescription: Use the Browserbase CLI (`browse`) for Browserbase Functions and platform API workflows. Use when the user asks to run `browse`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use the top-level `browse` driver commands (`browse open`, `browse get`, etc.) only when the user explicitly wants the CLI path.\ncompatibility: \"Requires the Browserbase CLI (`npm install -g browse`). API commands require `BROWSERBASE_API_KEY`.\"\nlicense: MIT\nallowed-tools: Bash\n---\n\n# Browserbase CLI\n\nUse the official `browse` CLI for Browserbase platform operations, Functions workflows, and Fetch API calls.\n\n## Setup check\n\nBefore using the CLI, verify it is installed:\n\n```bash\nwhich browse || npm install -g browse\nbrowse --help\n```\n\nFor authenticated commands, set the API key:\n\n```bash\nexport BROWSERBASE_API_KEY=\"your_api_key\"\n```\n\n## When to use this skill\n\nUse this skill when the user wants to:\n\n- run Browserbase commands through `browse`\n- scaffold, develop, publish, or invoke Browserbase Functions\n- inspect or manage Browserbase sessions, projects, contexts, or extensions\n- fetch a page through Browserbase without opening a browser session\n- search the web through Browserbase without opening a browser session\n- browse or scaffold starter templates with `browse templates`\n\n## When not to use this skill\n\n- For interactive browsing, page inspection, screenshots, clicking, typing, or login flows, prefer the `browser` skill.\n- For simple HTTP content retrieval where the user does not care about using the CLI specifically, the dedicated `fetch` skill is often a better fit.\n- Use the top-level driver commands (`browse open`, `browse get`, `browse click`, …) only when the user explicitly wants the CLI path or is already working in a `browse`-centric workflow.\n\n## Command selection\n\n- `browse functions` for local dev, packaging, publishing, and invocation\n- `browse cloud sessions`, `browse cloud projects`, `browse cloud contexts`, `browse cloud extensions` for Browserbase platform resources\n- `browse cloud fetch <url>` for Fetch API requests\n- `browse cloud search \"<query>\"` for Search API requests\n- `browse templates` to browse and scaffold starter templates\n- `browse open`, `browse get`, `browse click`, etc. for direct local/remote browser driving\n- `browse skills install` to install Browserbase agent skills for Claude Code\n\nFor local browser work, `browse open <url> --local` starts a clean isolated browser. Use `browse open <url> --auto-connect` only when you need to attach to an existing debuggable Chrome session.\n\n## Common workflows\n\n### Functions\n\n```bash\nbrowse functions init my-function\ncd my-function\nbrowse functions dev index.ts\nbrowse functions publish index.ts\nbrowse functions invoke <function_id> --params '{\"url\":\"https://example.com\"}'\n```\n\nUse `browse functions invoke --check-status <invocation_id>` to poll an existing invocation instead of creating a new one.\n\n### Platform APIs\n\n```bash\nbrowse cloud projects list\nbrowse cloud sessions create --proxies --verified --region us-east-1\nbrowse cloud sessions create --solve-captchas --context-id ctx_abc --persist\nbrowse cloud sessions get <session_id>\nbrowse cloud sessions downloads get <session_id> --output session-artifacts.zip\nbrowse cloud contexts create --body '{\"region\":\"us-west-2\"}'\nbrowse cloud extensions upload ./my-extension.zip\n```\n\n### Fetch API\n\n```bash\nbrowse cloud fetch https://example.com\nbrowse cloud fetch https://example.com --allow-redirects --output page.html\n```\n\n### Search API\n\n```bash\nbrowse cloud search \"browser automation\"\nbrowse cloud search \"web scraping\" --num-results 5\nbrowse cloud search \"AI agents\" --output results.json\n```\n\n### Templates\n\n```bash\nbrowse templates list\nbrowse templates list --tag Python --source Browserbase\nbrowse templates clone form-filling --language typescript\nbrowse templates clone amazon-product-scraping --language python ./my-scraper\n```\n\n## Best practices\n\n1. Prefer `browse --help` and subgroup `--help` before guessing flags.\n2. Use dash-case flags exactly as shown in CLI help.\n3. Use `--output <file>` on `browse cloud fetch` and `browse cloud search` to save results to a file.\n4. Use environment variables for auth unless the user explicitly wants one-off overrides.\n5. Pass structured request bodies with JSON strings in `--body` or `--params`.\n6. Remember that both `browse functions ...` and `browse cloud ...` use `--base-url` for API base URL overrides.\n\n## Troubleshooting\n\n- Missing API key: set `BROWSERBASE_API_KEY` or pass `--api-key`\n- Unknown flag: rerun the relevant command with `--help` and use the exact dash-case form\n- Command not found: re-run `npm install -g browse` and verify with `which browse`\n\nFor command-by-command reference and more examples, see [REFERENCE.md](REFERENCE.md).\n","contentSource":"skills.sh/api/download/browserbase/skills/browserbase-cli","contentFetchedAt":"2026-07-28T23:15:39.409Z"}