herdr
the runtime your coding agents live on
What is it?
What it is
A persistent runtime environment for AI agents and terminal-based workflows, providing a background server that hosts multiple terminal sessions and coordinates agent activity.
Why it exists
To create a unified, always-running platform where coding agents can operate seamlessly across terminals, share context, and maintain state even when disconnected or restarted.
Who should use it
Developers, AI engineers, and automation specialists who run autonomous AI coding agents (like Claude Code, Codex, Cursor) and need persistent, background terminal sessions with multi-agent orchestration capabilities.
Who should avoid it
Users looking for a lightweight, traditional terminal multiplexer (like standard tmux) without AI-specific orchestration overhead, or those who do not actively use AI coding agents in their daily workflow.
How it works
A quick walkthrough in plain English
How herdr works in 4 steps
Step 1 of 4
Something triggers the flow
A schedule, webhook, or manual click tells herdr to start.
Features
Advantages
- High reliability with always-active agent sessions
- Seamless integration with existing developer tools
- Flexible control via keyboard/mouse or tmux-style keys
- Performance benefits from Rust implementation
- Cross-platform compatibility via single binary
- Extensible through plugins for custom workflows
- Centralized session management with visibility into agent states
Disadvantages
- Learning curve for tmux-style keybindings
- Plugin ecosystem may require initial setup
- Rust dependency may limit accessibility for non-Rust users
- Agent-native design could complicate integration for some tools
- Potential complexity in managing multiple agents/sessions
Installation
cloud
Not specified in README
docker
Not specified in README
native
git clone https://github.com/herdrdev/herdr cd herdr cargo build --release
compose
Not specified in README
FAQ
How do I install herdr on different operating systems?
herdr can be installed via `curl -fsSL https://herdr.dev/install.sh | sh` for Unix-like systems, `brew install herdr` for macOS, `mise use -g herdr` for mise users, or `powershell -ExecutionPolicy Bypass -c "irm https://herdr.dev/install.ps1 | iex"` on Windows. Pre-built binaries are also available on the GitHub releases page.
How do I start and stop the herdr server?
Start herdr by running `herdr` in your terminal where the work lives. It runs as a background server. To detach from a session, use `ctrl+b q`, and reattach later by running `herdr` again. The server persists even when terminals are closed or machines restart.
How do coding agents interact with herdr?
Agents drive herdr through the CLI and socket API. They can spawn panes, prompt each other, and wait until another agent is genuinely blocked. This agent-native design allows seamless collaboration between different coding agents like Claude Code, Codex, and Cursor.
What agents are supported by herdr?
herdr supports multiple coding agents including Claude Code, Codex, Cursor, Opencode, Grok, and others. See the [supported agents documentation](https://herdr.dev/docs/agents/) for a complete list and integration details.
How do I extend herdr with plugins?
herdr supports plugins to extend panes and workflows. Browse the [plugin marketplace](https://herdr.dev/plugins/) to discover and install extensions that enhance your agent workflows and terminal management capabilities.
How do I build herdr from source for development?
Clone the repository with `git clone https://github.com/herdrdev/herdr`, navigate to the directory, and build using `cargo build --release`. Run `just test` for unit tests or `just check` for formatting, tests, and maintenance checks.
Featured in Videos
YouTube tutorials and walkthroughs for herdr
Alternatives
Similar projects ranked by category, topics, and text overlap.
