+ Most tools Herdr gets compared to are apps: a window you open to
+ manage coding agents, and a window the work depends on. Herdr is a
+ different kind of thing: a runtime. A server holds real terminals
+ open on the machine, the agents live in those, and every UI, ours
+ included, is just a client that attaches. Keep that split in mind
+ and the matrix below mostly explains itself.
+
+
+
+
-
-
-
-
-
+
+
+ herdr against the field
+ scrolls sideways on a phone
+
+
+
+
+
+
capability
+
herdr
+
tmux · zellij
+
cmux · warp
+
solo
+
conductor · emdash · superset
+
+
+
+
+
Kind of thing
+
runtime + clients
+
terminal multiplexer
+
terminal app
+
process dashboard
+
manager app
+
+
+
Work survives its own UI closing
+
yes, the server owns the terminals
+
yes, detach
+
session restore
+
while the app is open
+
while the app is open
+
+
+
Runs inside your existing terminal
+
yes
+
yes
+
replaces it
+
no, desktop app
+
no, desktop app
+
+
+
Semantic agent state
+
blocked · working · done · idle
+
—
+
attention cues
+
process status
+
workspace status
+
+
+
Detach, reattach, SSH in
+
yes, any tty
+
yes
+
partial
+
—
+
remote projects
+
+
+
Direct attach to one agent
+
yes
+
—
+
—
+
—
+
—
+
+
+
API agents drive themselves
+
read · send · wait · split · attach
+
terminal scripting
+
app APIs
+
MCP for processes
+
workflow APIs
+
+
+
Worktree and diff review flow
+
pairs with it
+
—
+
partial
+
—
+
yes, their core
+
+
+
Clients on the same runtime
+
TUI · CLI · plain SSH, more coming
+
its own client
+
the app only
+
the app only
+
the app only
+
+
+
+
+
+ The columns are categories, not enemies: Herdr pairs happily with a
+ worktree manager and runs fine inside a fancy terminal.
+ The row that sorts the field is the second one: what happens to
+ the agents when the thing you're looking at goes away.
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Compare Herdr
-
The agent multiplexer that lives in your terminal.
-
- Herdr gives coding agents the thing tmux gave terminal users:
- persistent real panes, detach and reattach, remote access, and a
- control surface. Then it adds agent state and an API the agents can use.
-
tmux persistence, agent awareness, no terminal replacement.
-
-
Runs inside your existing terminal
-
Owns persistent PTY sessions
-
Attaches locally, over SSH, or directly to one agent
-
Tracks blocked, working, done, and idle state
-
Exposes CLI and socket APIs agents can drive
-
-
-
-
-
-
-
-
The stack
-
Pick the center of gravity.
-
-
- The question is not whether a tool can run a terminal. Most can.
- The question is whether it combines terminal-native persistence with
- agent state and agent-controlled automation.
-
-
-
-
-
-
-
-
Capability
-
Herdr
-
tmux / Zellij
-
cmux / Warp
-
Solo
-
Conductor / Emdash / Superset
-
-
-
-
-
Runs inside your existing terminal
-
yes
-
yes
-
no, terminal app
-
no, desktop app
-
no, app workspace
-
-
-
Persistent PTY session runtime
-
yes
-
yes
-
session/app restore
-
managed processes
-
embedded terminals
-
-
-
Detach, reattach, and SSH in
-
yes
-
yes
-
partial
-
no
-
remote projects
-
-
-
Direct attach to one agent terminal
-
yes
-
no
-
no
-
no
-
no
-
-
-
Semantic agent state
-
blocked / working / done / idle
-
no
-
attention or native-agent status
-
process status
-
workspace status
-
-
-
Agent-shaped API
-
read, send, wait, split, attach
-
terminal scripting
-
app APIs
-
MCP for processes
-
workflow APIs
-
-
-
Git worktree and diff review flow
-
pairs with it
-
no
-
partial
-
no
-
yes
-
-
-
-
-
-
-
-
-
How Herdr differs
-
The intersection other tools miss.
-
-
-
- Herdr
-
Persistent terminal runtime, built for agents.
-
- Herdr keeps real terminal panes alive like a multiplexer, but treats agents
- as first-class runtime objects. You can scan state, jump to blocked work,
- attach directly to one agent, and let agents read, send, split, and wait
- through the CLI/socket API.
-
-
- existing terminal
- persistent PTYs
- SSH attach
- direct agent attach
- agent state
- agent API
-
-
-
-
- tmux / Zellij
-
Classic multiplexers stop at terminals.
-
They own panes and persistence. They do not know which pane is blocked, working, done, or ready for an agent wait.
-
-
- cmux / Warp
-
Terminal apps replace the terminal.
-
They can add polished desktop UX, but the workflow moves into their app. Herdr stays inside the terminal you already use.
-
-
- Solo
-
Dashboards supervise processes.
-
Process health and auto-restart are useful, but Herdr is about persistent interactive agent panes, not dev-stack supervision.
-
-
- Conductor / Emdash / Superset
-
Worktree tools own review flow.
-
They are for branch isolation, diffs, and PRs. Herdr is the live terminal layer those agents can run inside or alongside.
-
-
-
-
-
-
-
-
One-line comparisons
-
Use this when deciding.
-
-
- Herdr vs tmuxtmux persists terminals; Herdr persists agent workspaces and understands agent state.
- Herdr vs ZellijZellij is a modern terminal workspace; Herdr is an agent multiplexer with state, waits, and orchestration.
- Herdr vs cmuxcmux is a Mac terminal app for agents; Herdr is a terminal-native multiplexer that runs anywhere your terminal and SSH do.
- Herdr vs WarpWarp is an agentic development platform; Herdr is the local terminal control layer for your existing agents.
- Herdr vs OpenCode webOpenCode's web mode serves one agent over HTTP; Herdr is a terminal-native multiplexer for many agents and harnesses, reachable over plain SSH.
- Herdr vs SoloSolo manages your dev stack; Herdr manages persistent interactive agent panes.
- Herdr vs Conductor, Emdash, SupersetThey orchestrate isolated worktrees and review diffs; Herdr orchestrates live terminals and agent state.
-
-
-
-
-
Start with the multiplexer
-
If your agents live in terminals, put the terminals in Herdr.
-
- Install Herdr, run two agents, split a pane, then detach once. The difference is obvious when the agents keep running.
-
+ A server owns the terminals; every UI is a client of it. The TUI in
+ the screenshots attaches, detaches and even crashes without the
+ agents noticing. Same for the CLI, plain SSH, and whatever
+ attaches next. The TUI is the first client, not the last.
+
-
-
-
-
settings
-
theme
-
-
dark
-
-
-
-
-
-
-
-
-
-
-
-
light
-
-
-
-
-
-
-
-
-
-
+
+
herdr-serverup
+
4 agents · 0 clients attached · still working
+
+
+
02
+
+
Multiplexers persist terminals, not agents.
+
+ tmux gave humans persistence, and Herdr keeps that whole
+ inheritance: real PTYs, detach, SSH. What it adds is the part
+ multiplexers never had: knowing which pane is an agent, whether
+ it's blocked, and how to wait on it instead of polling it.
+
+
+
+
tmux ls3 sessions
+
which one is waiting on you? no idea
+
+
+
+
03
+
+
Terminal apps replace your terminal.
+
+ cmux and Warp can be genuinely polished, but the deal is that the
+ work moves into their window, with their renderer, on the machines
+ they support. Herdr changes nothing about your terminal. It runs
+ inside it, wherever a terminal and SSH already reach.
+
+
+
+
ghostty · kitty · iterm · alacrittykept
+
herdr runs in the one you already chose
+
+
+
+
04
+
+
Manager apps are clients without a runtime.
+
+ Conductor, Emdash and Superset manage a herd from a window:
+ worktrees, diffs, review queues. Useful, and Herdr pairs fine with
+ that flow. But a window that manages agents is not a place agents
+ live: quit the app and the herd goes with it.
+
+
+
+
their app quitsagents stop
+
every herdr client quitsagents keep going
+
+
+
+
05
+
+
Dashboards watch processes.
+
+ Solo supervises a dev stack: health, restarts, logs. Herdr's job
+ is different: interactive agent terminals that stay open, hold
+ scrollback and state, and stay yours whether or not anything is
+ watching them.
+
+
+
+
process statusup / down
+
agent stateblocked · working · idle
+
+
+
-
-
-
+
+
+
+
A runtime, not another window.
+
+ Install it and nothing about your setup changes: same terminal, same
+ agent CLIs. They just stop dying when a window does.
+