herdr-browser

name	herdr-browser
description	Connect browser automation tools to a Chromium view rendered inside a Herdr browser pane.

Herdr Browser

Use this skill when the user wants Browser Use, PinchTab, Playwright, Chrome DevTools MCP, or another CDP client to control the browser visible in Herdr.

Do not install herdr-browser globally. Discover the installed or linked plugin root by running:

herdr plugin list --plugin official.browser --json

Read result.plugins[0].plugin_root from the JSON response. Run the CLI with Bun from any working directory:

bun run "<plugin_root>/src/cli.ts"

List live browser views before connecting:

bun run "<plugin_root>/src/cli.ts" views

Select the intended view from its view_id, pane_id, URL, title, and tabs. Never guess when more than one view is present. Connect with:

bun run "<plugin_root>/src/cli.ts" connect --view <view_id>

The response contains a view-scoped cdp_http_url, browser_ws_url, and the currently active target. Use the browser-level endpoint so the automation tool can create, inspect, select, and close multiple tabs in that view.

Standard CDP Target.createTarget, Target.activateTarget, Page.bringToFront, and Target.closeTarget operations synchronize with the Herdr tab strip and rendered target. A tool that changes only its own internal selected-page state must also bring that page to front; local tool state is not observable through CDP.

Tool bootstrap:

• Browser Use: set BU_CDP_URL to cdp_http_url or BU_CDP_WS to browser_ws_url.
• PinchTab: enable its external attach policy, then attach a bridge to browser_ws_url or cdp_http_url.
• Playwright: call chromium.connectOverCDP(cdp_http_url).
• Playwright MCP: pass --cdp-endpoint=<cdp_http_url>.
• Chrome DevTools MCP: pass --browser-url=<cdp_http_url>.

Herdr Browser owns Chromium lifecycle. Closing a connected automation client disconnects it from the gateway without terminating Chromium. Closing the Herdr browser pane closes its view and gateway.