Obra Superpowers Chrome
obra-superpowers-chrome is a Claude Code plugin for the Ship phase that gives your agent direct Chrome browser control via the DevTools Protocol with no extra dependencies.
by obra · github.com/obra/superpowers-chrome
Give Claude Code direct Chrome control through the DevTools Protocol so you can automate clicks, navigation, and inspection with no extra browser-driver dependencies.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install obra-superpowers-chrome@obra/superpowers-chromeBuilt 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:obra/superpowers-chrome") and the paste-ready config with skillselion.get_install_config("plugin:obra/superpowers-chrome").
What it does
obra-superpowers-chrome is a Claude Code plugin from the Superpowers line that exposes direct Google Chrome control through the Chrome DevTools Protocol, advertising zero extra dependencies so your agent can drive a real browser without bolting on a separate automation stack. It is aimed at indie and solo builders who already ship with Claude Code and want quick, in-session browser access for prototyping checks, UI debugging, and lightweight smoke tests rather than maintaining a full E2E framework. Because it speaks DevTools natively, it slots into agent-tooling and testing moments across validate, build, and ship—especially when you need to see what production CSS and JavaScript actually do. It is not a replacement for CI-grade test runners or cloud browser grids; it is a fast path to human-visible verification while the agent codes. Install it when you want Claude to open pages, interact with the DOM, and iterate with you in one toolchain.
Highlights
- Direct Chrome control via DevTools Protocol with zero additional runtime dependencies
- Fits the Superpowers ecosystem as a lightweight browser skill for Claude Code
- Useful for live page inspection, navigation, and interaction without installing Playwright or Puppeteer
- Autostart-oriented workflow keywords suggest Chrome can be spun up when the skill invokes
- Single-plugin bundle focused purely on browser access, not full test-suite scaffolding
Why builders use it
You need the agent to verify real browser behavior but do not want to install and maintain Playwright, Puppeteer, or a separate driver layer just to click through your app.
After you add the plugin, Claude can drive Chrome through DevTools for navigation and inspection during debugging and smoke checks without pulling in another automation stack.
At a glance
- Type - Plugin in Automation.
- Adoption - 0 installs, 232 stars, 0 votes.
FAQ
Who is obra-superpowers-chrome for?
It is for Claude Code users in the Superpowers ecosystem who want the agent to control Chrome directly for quick verification and debugging without extra browser libraries.
When should I use obra-superpowers-chrome?
Use it when you need live browser interaction—staging smoke tests, reproducing a UI bug, or walking a prototype—during validate, build, or ship work.
How do I add obra-superpowers-chrome to my agent?
Register the obra/superpowers-chrome Claude Code plugin from the repo catalog, ensure Chrome is available locally, then invoke the Superpowers Chrome skill when you want DevTools-driven control.
Comments
Share how you use obra-superpowers-chrome, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.