by SawyerHood
A Claude Skill to give your agent the ability to use a web browser
# Add to your Claude Code skills
git clone https://github.com/SawyerHood/dev-browserA browser automation plugin for Claude Code that lets Claude control your browser to test and verify your work as you develop.
Key features:
/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.
No comments yet. Be the first to share your thoughts!
Installation:
extension.zip from the latest release~/.dev-browser-extension)chrome://extensionsUsing the extension:
When active, Claude can control your existing Chrome tabs with all your logged-in sessions, cookies, and extensions intact.
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"
| Method | Time | Cost | Turns | Success | | ----------------------- | ------- | ----- | ----- | ------- | | Dev Browser ...