Sawyerhood Dev Browser
sawyerhood-dev-browser is a Claude Code plugin for the Build phase that gives your coding agent Playwright-backed web browsing with persistent session state for automation, debugging, and testing.
by SawyerHood · github.com/SawyerHood/dev-browser
Give Claude Code (or similar) a Playwright-backed browser skill so the agent can navigate sites, capture state, and debug flows without you driving every click.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install sawyerhood-dev-browser@SawyerHood/dev-browserBuilt 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:SawyerHood/dev-browser") and the paste-ready config with skillselion.get_install_config("plugin:SawyerHood/dev-browser").
What it does
sawyerhood-dev-browser is a Claude Code plugin that wraps browser control so your agent can open pages, interact with DOM, and keep context across steps using Playwright-style automation. Solo builders use it when a product depends on real web behavior—OAuth redirects, dynamic SPAs, or competitor flows—that static HTTP clients miss. It sits in the build phase as agent-tooling but naturally supports prototype checks during validate and manual-style regression during ship. The README positions it as a skill that gives agents a real browser rather than guessing from HTML snippets. You install the plugin, invoke the skill when tasks need navigation or verification, and the agent can drive repeatable browser sessions with persistent state. It is not a hosted browser farm or a replacement for CI browsers; it is local agent tooling for faster iteration when you are shipping with Claude Code and want eyes-on-the-web without context-switching to your own browser.
Highlights
- Playwright-based web browsing exposed as a Claude skill for developers and agents
- Persistent browser state across turns so sessions survive multi-step workflows
- Supports automation, live debugging, and testing-oriented agent workflows
- Community plugin bundle (1 plugin) from SawyerHood/dev-browser
- Fits agent-led validation of UI and third-party integrations before full test suites
Why builders use it
Agents cannot reliably verify real web apps when they only read static code or one-off fetches, so integration and UI bugs slip through until you manually click every path.
After you add the plugin, your agent can run multi-step browser workflows with retained state so you validate flows and debug faster without leaving the editor.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 5.5k stars, 0 votes.
FAQ
Who is sawyerhood-dev-browser for?
Solo and indie developers using Claude Code who want their agent to drive a real browser for testing, debugging, and automation instead of inferring behavior from code alone.
When should I use sawyerhood-dev-browser?
Use it during build and early ship when you need the agent to log in, click through SPAs, capture errors, or repeat a flow with the same browser context across prompts.
How do I add sawyerhood-dev-browser to my agent?
Install the plugin from the SawyerHood/dev-browser repository into Claude Code, enable the bundled skill, and invoke it when tasks require navigation or live page verification.
Comments
Share how you use sawyerhood-dev-browser, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.