Tool roles, alternatives, selection tradeoffs, and compatibility caveats.
Terminal workspace / agent multiplexers
John uses: Herdr (ogulcancelik/herdr, 17.3k, AGPL-3.0) — "tmux for agents": panes plus an agent-state sidebar (blocked/working/done/idle auto-detected for 15+ agents), detach/reattach, and — the part section 06 is built on — a unix-socket API that agents themselves can drive: spawn panes, read sibling output, wait on each other. That socket is what makes the keeper prompt ("keep other panes alive") and planned swarms one-keystroke moves.
| Alternative | What it is | How it differs | License |
|---|---|---|---|
| tmux | The standard terminal multiplexer | No agent-state awareness or agent API; fully scriptable via send-keys/capture-pane so you can hand-roll herdr-like patterns | ISC |
| Zellij | Terminal workspace with batteries included (layouts, plugins in WASM) | Friendlier defaults and a plugin system, but agent-agnostic — no built-in agent status model | MIT |
| claude-squad | Manage multiple AI terminal agents (Claude Code, Codex, OpenCode, Amp) in one TUI | Purpose-built agent manager like herdr, backed by tmux + git worktrees; narrower pane model | AGPL-3.0 |
| Vibe Kanban | Kanban web UI for orchestrating multiple coding-agent tasks | Board-of-tasks metaphor instead of terminal panes; good for reviewing parallel agent work; check current repository activity | Apache-2.0 |
| hcom | Lets AI agents message, watch, and spawn each other across terminals (Claude Code, Codex, Antigravity, Pi, ...) | Agent-to-agent communication layer without owning your terminal layout; closest OSS match to herdr's socket API idea | MIT |
| Omnara | Talk to your AI agents from anywhere (mobile/web control plane, YC S25) | Remote monitoring/answering of agents rather than local pane management; check current repository activity | Apache-2.0 |
Pick this if…
- tmux — you want the zero-risk default;
send-keys/capture-panelet you hand-roll herdr's socket tricks. - Zellij — you want modern ergonomics and a plugin system without agent-specific features.
- claude-squad — you specifically want "many agents, one dashboard" with worktree isolation.
- Vibe Kanban — you'd rather review parallel agent work as a board than as panes (note: quieter repo lately).
- hcom — you want the agent-to-agent messaging half of herdr as a small composable tool.
- Omnara — your bottleneck is being away from the keyboard, not pane management.