Browserbase Claude Code Plugin
Browserbase Claude Code Plugin is a Claude Code plugin for the Ship phase that runs agent browser automation on Browserbase cloud browsers instead of local Chrome.
by browserbase · github.com/browserbase/claude-code-plugin
Route Claude Code browser automation through Browserbase cloud browsers instead of local Chrome for sandboxed testing and debugging.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install browserbase-claude-code-plugin@browserbase/claude-code-pluginBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:browserbase/claude-code-plugin") and the paste-ready config with skillselion.get_install_config("plugin:browserbase/claude-code-plugin").
What it does
The Browserbase Claude Code plugin connects Claude Code to Browserbase so agents use cloud-hosted browsers instead of relying on local Chrome. Solo builders validating web apps, extensions, or agent-built frontends often hit friction when CI laptops differ, headless setup is painful, or they need isolated sessions for untrusted automation. This plugin provides that remote execution layer: sandboxed browsers, session-oriented debugging, and recording-oriented workflows described in the marketplace listing. It is phase-specific to ship-time verification and interactive debugging rather than journey-wide methodology. Complexity is beginner to intermediate depending on your Browserbase account and API setup. Pair it with frontend build work when you want the same browser environment locally and in the cloud. It is an automation integration plugin, not a replacement for your test runner or Playwright config—you still own assertions and suite structure.
Highlights
- Replaces local Chrome with Browserbase managed cloud browsers inside Claude Code.
- Sandboxed, secure remote sessions for automation and debugging workflows.
- Session recording support for reproducing agent-driven browser steps.
- Single-plugin integration focused on browser execution—not a full E2E framework.
- Useful when local browser installs or environments block consistent agent testing.
Why builders use it
Local Chrome dependencies make agent browser testing inconsistent, hard to sandbox, and painful on minimal dev machines.
After install, Claude Code drives secure cloud browser sessions with recording-friendly debugging instead of tying automation to local Chrome.
At a glance
- Type - Plugin in Automation.
- Adoption - 0 installs, 67 stars, 0 votes.
FAQ
Who is browserbase-claude-code-plugin for?
Developers using Claude Code to test or debug web apps who prefer Browserbase cloud browsers over local Chrome.
When should I use browserbase-claude-code-plugin?
Use it during ship-phase UI verification, agent-driven exploration, or debugging when you need sandboxed remote browser sessions.
How do I add browserbase-claude-code-plugin to my agent?
Install browserbase/claude-code-plugin from the Claude Code marketplace and configure Browserbase API credentials per the repo README.
Comments
Share how you use browserbase-claude-code-plugin, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.