Compare · Deep dive
dev-mux vs herdr
herdr is the breakout agent multiplexer of 2026 — "tmux for coding agents," roughly 23k GitHub stars within months, and genuinely excellent on a single machine. So let's be clear up front: this is not a rivalry. herdr and dev-mux live on different layers of the same stack, and for a lot of people the right answer will be both.
What herdr actually is
herdr replaces tmux with an agent-native workspace: panes and tabs like you'd expect,
plus a semantic sidebar that knows each agent's state — idle, working, blocked,
done — with automatic detection of agents like Claude Code, sane default
keybindings, modern protocol support, and a scriptable JSON socket API. It's a single
binary, Apache-2.0, and can attach to a remote server over SSH
(herdr --remote box) while keeping your local keybindings.
At a glance
As of July 31, 2026. If something here is stale, tell us.
| dev-mux | herdr | |
|---|---|---|
| Layer | Fleet control plane (above the multiplexer) | Box-level multiplexer (replaces tmux) |
| Scope | Every machine, repo, and agent — one live map | One machine per view (local or over SSH) |
| Agent awareness | Hook-level signals (waiting / done / error), attention escalation, usage | Semantic per-pane state (idle / working / blocked / done), auto-detection |
| Always-on watcher | Yes — hub polls even when no terminal is open; stale state flagged in seconds | No — state lives in your attached session |
| Machine health | CPU/mem per box, liveness, roster | — |
| Surfaces | Browser cockpit, TUI, iOS, G2 glasses, Telegram | Your terminal |
| Relationship to tmux | Runs on it (spoke floor: bash 3.2 + tmux + git) | Replaces it |
| Automation surface | --dry-run plan seam, signals, action plane | JSON socket API + CLI (--json everywhere) |
| License / price | Commercial — Solo $25/mo · Team $100/mo | Apache-2.0, free |
Where herdr shines
- The one-box agent experience — the semantic sidebar is the best in-terminal answer yet to "which of my agents needs me," and detection needs zero configuration.
- Modern where tmux is crusty — keybindings that don't fight your editor, image protocol support, notifications that pass through correctly.
- Scriptability — the JSON socket API is clean, versioned, and a pleasure to build against (we know; we've tested it).
Where dev-mux is a different layer
- The fleet is the unit. herdr shows you the herd on the box you're attached to. dev-mux's hub is awake when your terminal isn't — polling every machine, aggregating every agent, flagging anything stale within seconds, and pushing attention signals to whatever surface you're carrying.
- State beyond the terminal. Machine health, provider usage dials, a roster with roles, worktree session verbs, Linear wiring — fleet-operations concerns that don't belong inside a multiplexer, and aren't in one.
- Surfaces beyond the terminal. A browser cockpit with live terminals, an iOS app, glasses, Telegram — the fleet follows you off the keyboard.
- Heterogeneous floors. Anything with bash 3.2 + tmux + git is a spoke today — decade-old MacBooks included. herdr is a modern single binary, but it's still one more thing each box must run.
Better together
Here's the part we're genuinely excited about: herdr exposes exactly the seam a fleet layer wants. Its socket API reports semantic agent state that's richer than what heuristics can infer from a raw tmux pane, and its attach command fits the same terminal-relay pattern we use for tmux. We've verified the integration path hands-on: the hub can poll herdr the way it polls tmux, and herdr's blocked / working / done / idle map cleanly onto dev-mux's attention model. herdr-aware fleet polling is on our near-term roadmap — the goal is that a herdr box joins your fleet map as a first-class citizen, sidebar semantics and all. Today, the spoke floor is tmux.
Common questions
Is dev-mux a herdr alternative?
Different layers: herdr is the multiplexer on a box; dev-mux is the control plane over all your boxes. One box → herdr may be plenty. Many boxes → that's us (and, soon, us watching your herdr boxes too).
Can I use herdr and dev-mux together?
That's the plan — we've verified the integration path and herdr-aware polling is on the near-term roadmap. Today the spoke floor is tmux.
Does herdr work across multiple machines?
One at a time, including remotely over SSH — but there's no cross-machine map, health, or always-on watcher. That aggregation is the layer dev-mux adds.
herdr runs the herd on a box. dev-mux watches every herd you have.
Get early accessWritten 2026-07-31 against herdr's public site, docs, and a hands-on evaluation of herdr 0.7.5. herdr is a trademark of its authors; no affiliation or endorsement implied. Corrections welcome.