A browser automation plugin for Claude Code that lets Claude control your web browser to close the loop on your development workflows.
This plugin is optimized for testing and verifying as you develop. Claude can interact with your running application, fill out forms, click buttons, and verify that your changes work—all without leaving your coding session.
| Approach | How It Works | Tradeoff |
|---|---|---|
| Playwright MCP | Observe-think-act loop with individual tool calls | Simple but slow; each action is a separate round-trip. The MCP also takes up a lot of context window space. |
| Playwright skill | Full scripts that run end-to-end | Fast but fragile; scripts start fresh every time, so failures mean starting over. Very context efficient. |
| Dev Browser | Stateful server + agentic script execution | Best of both worlds. In between Playwright MCP and Playwright skill in terms of context efficiency. In practice it can be more context efficient because it is less likely to get stuck. |
Dev Browser runs a persistent Playwright server that maintains browser state across script executions. This means:
- Pages stay alive - Navigate to a page once, interact with it across multiple scripts
- Flexible execution - Run full Playwright scripts when the agent knows what to do, or fall back to step-by-step observation when exploring
- Codebase-aware - The plugin includes instructions for Claude to look at your actual code to inform debugging
- LLM-friendly inspection - Get structured DOM snapshots optimized for AI understanding, similar to browser-use
In practice, Claude will often explore a page step-by-step first, then generate reusable scripts to speed up repetitive actions.
- Claude Code CLI installed
- Bun runtime (v1.0 or later)
curl -fsSL https://bun.sh/install | bash
In Claude Code, run:
/plugin marketplace add sawyerhood/dev-browser
/plugin install dev-browser@sawyerhood/dev-browser
Prompt Claude to use it!
Restart Claude Code after installation to activate the plugin.
Amp automatically detects skills from your .claude/skills directory with zero configuration required.
Note: Since Amp can't run background processes, you'll need to manually start the dev-browser server in a separate terminal before using this skill.
# Create skills directory if it doesn't exist
mkdir -p ~/.claude/skills
# Clone the repo and copy the skill
git clone https://github.com/sawyerhood/dev-browser /tmp/dev-browser-skill
cp -r /tmp/dev-browser-skill/skills/dev-browser ~/.claude/skills/dev-browser
rm -rf /tmp/dev-browser-skillBefore using the skill, start the dev-browser server in a separate terminal:
cd ~/.claude/skills/dev-browser
bun install # First time only
bun run start-serverKeep this terminal running while you use Amp.
Prompt Claude to use it! Amp will automatically load the skill when needed.
Learn more about Amp's skill support.
By default, Claude will prompt for permission on every script execution. You can configure it to allowlist specific commands to bypass this.
You can also run it in YOLO mode bypassing all permission prompts:
claude --dangerously-skip-permissionsNote: This skips all security prompts, so only use in trusted environments.
Add to your ~/.claude/settings.json (user-level, applies to all projects):
{
"permissions": {
"allow": ["Bash(bun x tsx:*)"]
}
}This allowlists the bun x tsx command that runs the browser automation scripts, regardless of which directory the skill is installed in.
For project-level settings, add to .claude/settings.json in your project root.
Once installed, just ask Claude to interact with your browser. Here are some example prompts:
Testing your app:
"Open my local dev server at localhost:3000 and create an account to verify the signup flow"
Debugging UI issues:
"Go to the settings page and figure out why the save button isn't working"
Close the loop visually
"Can you use the frontend design skill to make the landing page more visually appealing? Use dev-browser to iterate on the design until it looks good."
Averaged over 3 runs per method. See dev-browser-eval for methodology.
| Method | Time | Cost (USD) | Turns | Success Rate |
|---|---|---|---|---|
| Dev Browser | 3m 53s | $0.88 | 29 | 100% (3/3) |
| Playwright MCP | 4m 31s | $1.45 | 51 | 100% (3/3) |
| Playwright Skill | 8m 07s | $1.45 | 38 | 67% (2/3) |
Dev Browser advantages:
- 14% faster than Playwright MCP, 52% faster than Playwright Skill
- 39% cheaper than both alternatives
- 43% fewer turns than Playwright MCP, 24% fewer than Playwright Skill
MIT