Dev Browser - Browser automation for Claude Code

A browser automation plugin for Claude Code that lets Claude control your browser to test and verify your work as you develop.

Key features:

• Persistent pages - Navigate once, interact across multiple scripts
• Flexible execution - Full scripts when possible, step-by-step when exploring
• LLM-friendly DOM snapshots - Structured page inspection optimized for AI

• Claude Code CLI installed
• Node.js (v18 or later) with npm

/plugin marketplace add sawyerhood/dev-browser
/plugin install dev-browser@sawyerhood/dev-browser

Restart Claude Code after installation.

Copy the skill to your skills directory:

# For Amp: ~/.claude/skills | For Codex: ~/.codex/skills
SKILLS_DIR=~/.claude/skills # or ~/.codex/skills
mkdir -p $SKILLS_DIR
git clone https://github.com/sawyerhood/dev-browser /tmp/dev-browser-skill
cp -r /tmp/dev-browser-skill/skills/dev-browser $SKILLS_DIR/dev-browser
rm -rf /tmp/dev-browser-skill

Amp only: Start the server manually before use:

cd ~/.claude/skills/dev-browser && npm install && npm run start-server

The Chrome extension allows Dev Browser to control your existing Chrome browser instead of launching a separate Chromium instance. This gives you access to your logged-in sessions, bookmarks, and extensions.

Installation:

1. Download extension.zip from the latest release
2. Unzip the file to a permanent location (e.g., ~/.dev-browser-extension)
3. Open Chrome and go to chrome://extensions
4. Enable "Developer mode" (toggle in top right)
5. Click "Load unpacked" and select the unzipped extension folder
6. Click the extension icon in Chrome toolbar and toggle it to "Active"

When active, the extension connects to Dev Browser's server and allows automation of your current Chrome tabs. Tell your agent to "use the extension" or "use my existing Chrome" to use it instead of the built-in browser.

To skip permission prompts, add to ~/.claude/settings.json:

{
 "permissions": {
 "allow": ["Skill(dev-browser:dev-browser)", "Bash(npx tsx:*)"]
 }
}

Or run with claude --dangerously-skip-permissions (skips all prompts).

Just ask Claude to interact with your browser:

"Open localhost:3000 and verify the signup flow works"

"Go to the settings page and figure out why the save button isn't working"

See dev-browser-eval for methodology.

MIT

Sawyer Hood