salamituns

Herdr Browser — Development skill for Claude Code

Development community

Watch your coding agents browse: a Herdr pane showing the Chrome that Claude Code, Codex, Cursor and Antigravity drive through chrome-devtools-mcp.

How to install Herdr Browser

This entry records only its repository, not the path inside it, so there is no exact command to give. Open salamituns/herdr-browser and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Herdr Browser does

Watch your coding agents browse: a Herdr pane showing the Chrome that Claude Code, Codex, Cursor and Antigravity drive through chrome-devtools-mcp. Drop-in, no new agent tools.

Alternatives in Development

Chrome Devtools MCP — Chrome DevTools for coding agents 29504 108 1 31.7k ★
Herdr Reviewr — Review your coding agent's diff in a terminal pane and send line comments back to Claude Code, Codex, OpenCode 823 ★
Zoetrope — Watch a Claude Code session as a live flow graph, in your terminal or your browser 584 ★

README

herdr-browser

**Watch your coding agents use the browser, inside [Herdr](https://github.com/herdrdev/herdr).**

Claude Code, Codex, Cursor and Antigravity drive Chrome through the Chrome DevTools MCP server (`chrome-devtools-mcp`), but that Chrome is usually invisible. This plugin shows it in a Herdr pane next to the agent, live, and lets you click and type into the same page. Your agents keep the `chrome-devtools` tools they already use: nothing new to install in the agent, nothing new for it to learn.

agent pane (workspace w8)                     browser pane (w8)
   └─ mcp.js → chrome-devtools-mcp ──┐   ┌── main.js (follows new tabs)
                                     ▼   ▼
                     headless Chrome for w8 (one per workspace)
                     started on first use, stopped when the workspace closes

A drop-in for chrome-devtools-mcp. Point your existing chrome-devtools MCP entry at the plugin's launcher. Inside Herdr it drives the workspace's visible Chrome; anywhere else it runs plain chrome-devtools-mcp, unchanged.
The pane opens itself next to the agent the first time it uses a browser tool, and switches to each tab the agent opens.
One Chrome per Herdr workspace, with its own cookies and logins, started on the first browser call.
Take over at any time: mouse, keyboard, scrolling and the URL bar go to the same page. Phone emulation by the agent is shown at its real proportions.

v0.2.0, macOS and Linux. Looking for a general-purpose browser in the terminal instead? See [Related projects](#related-projects).

Let your agent set it up

In an agent running inside a Herdr pane, paste:

Set up the herdr-browser Herdr plugin for me by following
https://raw.githubusercontent.com/salamituns/herdr-browser/main/agent-guide.md

[`agent-guide.md`](agent-guide.md) has the agent check the requirements, install the plugin, repoint your existing `chrome-devtools` entries (backing up each conf