herdr-browser
Render a real Chromium view inside a Herdr pane and drive it over CDP.
What is it?
What it is
A Herdr plugin that renders a live Chromium browser view within a Herdr pane, enabling interactive automation and local development preview.
Why it exists
To provide a visible, interactive browser interface for automation control and local server testing without detaching from the terminal.
Who should use it
Automation engineersQA testersWeb developersTerminal-centric developersDevOps engineers
Who should avoid it
Windows usersUsers without a Kitty-compatible terminal (e.g., Ghostty, WezTerm)Users requiring full browser features like DevTools, extensions, or IMEUsers working over remote SSH connections with limited bandwidth
How it works
A quick walkthrough in plain English
How herdr-browser works
Step 1 of 3
You interact with it
Open herdr-browser, send a request, or connect it to your stack.
Features
Advantages
- Eliminates the gap between invisible automation and visual observation
- Allows manual intervention in automated workflows without disconnecting
- Enables previewing local development servers directly in the terminal
- Provides a seamless, integrated workflow for browser automation debugging
- Low-latency rendering via paint-driven backpressure
Disadvantages
- Not a general-purpose browser (lacks DevTools, extensions, and downloads)
- Limited platform support (Linux and macOS only; no Windows)
- High bandwidth requirements (not suitable for remote SSH use)
- Missing features like text selection, clipboard, and find-in-page
- No automatic Chromium download (requires existing installation)
Installation
FAQ
How do I install Herdr Browser?
Install via `herdr plugin install ogulcancelik/herdr-browser --yes` or link a local checkout with `herdr plugin link ~/Projects/herdr-browser`.
What system requirements are needed?
Herdr 0.7.4+, Linux/macOS, Bun, Google Chrome/Chromium, and a Kitty-compatible terminal like kitty or WezTerm.
How do I open a browser pane?
Use `herdr plugin pane open --plugin official.browser --entrypoint browser` with placement options like `split`, `tab`, or `overlay`.
How can I control the browser from an automation client?
Run `bun run '<plugin_root>/src/cli.ts' connect --view <view_id>` to get CDP endpoints for tools like Playwright or Browser Use.
How do local development links trigger the browser?
Control-click (or Cmd-click on macOS) URLs with `localhost`, `127.0.0.1`, or `[::1]` in Herdr terminals to open them in a browser pane.
What are the current limitations?
Unsupported features include downloads, DevTools, right-click menus, IME, and page text selection. Rendering requires Kitty graphics and is optimized for local sessions.
Featured in Videos
YouTube tutorials and walkthroughs for herdr-browser
Alternatives
Similar projects ranked by category, topics, and text overlap.
