browserbase-cli▌
browserbasehq/cli · updated May 5, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Use the Browserbase CLI (`bb`) for Browserbase Functions and platform API workflows.
| name | browserbase-cli |
| description | Use the Browserbase CLI (`bb`) for Browserbase Functions and platform API workflows. Use when the user asks to run `bb`, 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 `bb browse` only when the user explicitly wants the Browserbase CLI path. |
| compatibility | "Requires the Browserbase CLI (`npm install -g @browserbasehq/cli`). API commands require `BROWSERBASE_API_KEY`. `BROWSERBASE_PROJECT_ID` is only needed for `bb functions dev` and `bb functions publish`. `bb browse` additionally requires `npm install -g @browserbasehq/browse-cli`." |
| license | MIT |
| allowed-tools | Bash |
Browserbase CLI
Use the official bb CLI for Browserbase platform operations, Functions workflows, and Fetch API calls.
Setup check
Before using the CLI, verify it is installed:
which bb || npm install -g @browserbasehq/cli
bb --help
For authenticated commands, set the API key:
export BROWSERBASE_API_KEY="your_api_key"
If using bb functions dev or bb functions publish, also set:
export BROWSERBASE_PROJECT_ID="your_project_id"
When to use this skill
Use this skill when the user wants to:
- run Browserbase commands through
bb - scaffold, develop, publish, or invoke Browserbase Functions
- inspect or manage Browserbase sessions, projects, contexts, or extensions
- fetch a page through Browserbase without opening a browser session
- search the web through Browserbase without opening a browser session
- browse or scaffold starter templates with
bb templates
When not to use this skill
- For interactive browsing, page inspection, screenshots, clicking, typing, or login flows, prefer the
browserskill. - For simple HTTP content retrieval where the user does not care about using the CLI specifically, the dedicated
fetchskill is often a better fit. - Use
bb browse ...only when the user explicitly wants the CLI wrapper or is already working in abb-centric workflow.
Command selection
bb functionsfor local dev, packaging, publishing, and invocationbb sessions,bb projects,bb contexts,bb extensionsfor Browserbase platform resourcesbb fetch <url>for Fetch API requestsbb search "<query>"for Search API requestsbb templatesto browse and scaffold starter templatesbb browse ...to forward to the standalonebrowsebinary (requires@browserbasehq/browse-cli)bb skills installto install Browserbase agent skills for Claude Code
For bb browse, the standalone browse CLI behavior is the source of truth: bb browse env local uses a clean isolated local browser by default, and bb browse env local --auto-connect opts into reusing an existing local Chrome session.
Common workflows
Functions
bb functions init my-function
cd my-function
bb functions dev index.ts
bb functions publish index.ts
bb functions invoke <function_id> --params '{"url":"https://example.com"}'
Use bb functions invoke --check-status <invocation_id> to poll an existing invocation instead of creating a new one.
Platform APIs
bb projects list
bb sessions create --proxies --advanced-stealth --region us-east-1
bb sessions create --solve-captchas --context-id ctx_abc --persist
bb sessions get <session_id>
bb sessions downloads get <session_id> --output session-artifacts.zip
bb contexts create --body '{"region":"us-west-2"}'
bb extensions upload ./my-extension.zip
Fetch API
bb fetch https://example.com
bb fetch https://example.com --allow-redirects --output page.html
Search API
bb search "browser automation"
bb search "web scraping" --num-results 5
bb search "AI agents" --output results.json
Templates
bb templates list
bb templates list --language python
bb templates clone form-filling --language typescript
bb templates clone amazon-product-scraping --language python ./my-scraper
Best practices
- Prefer
bb --helpand subgroup--helpbefore guessing flags. - Use dash-case flags exactly as shown in CLI help.
- Use
--output <file>onbb fetchandbb searchto save results to a file. - Use environment variables for auth unless the user explicitly wants one-off overrides.
- Pass structured request bodies with JSON strings in
--bodyor--params. - Remember that
bb functions ...uses--api-url, while platform API commands use--base-url. - If
bb browsefails becausebrowseis missing, either install@browserbasehq/browse-clior switch to thebrowserskill.
Troubleshooting
- Missing API key: set
BROWSERBASE_API_KEYor pass--api-key - Missing project ID on
bb functions devorbb functions publish: setBROWSERBASE_PROJECT_IDor pass--project-id - Unknown flag: rerun the relevant command with
--helpand use the exact dash-case form bb browseinstall error: runnpm install -g @browserbasehq/browse-cli
For command-by-command reference and more examples, see REFERENCE.md.
How to use browserbase-cli on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add browserbase-cli
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches browserbase-cli from GitHub repository browserbasehq/cli and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate browserbase-cli. Access the skill through slash commands (e.g., /browserbase-cli) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★71 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
browserbase-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Jin Gill· Dec 28, 2024
browserbase-cli has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Min Liu· Dec 24, 2024
I recommend browserbase-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Emma Perez· Dec 12, 2024
Solid pick for teams standardizing on skills: browserbase-cli is focused, and the summary matches what you get after install.
- ★★★★★Piyush G· Nov 19, 2024
browserbase-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Min Garcia· Nov 19, 2024
Solid pick for teams standardizing on skills: browserbase-cli is focused, and the summary matches what you get after install.
- ★★★★★Nikhil Malhotra· Nov 15, 2024
Useful defaults in browserbase-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★James Lopez· Nov 3, 2024
browserbase-cli has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Emma Gill· Oct 22, 2024
browserbase-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Oct 10, 2024
browserbase-cli has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 71