cccc vs herdr
Group-chat orchestration for coding agents: Claude Code, Codex, ChatGPT Web and others in one durable group with an append-only ledger, read receipts, and Web/IM/mobile ops. — versus — Agent multiplexer for your terminal: every Claude Code/Codex session in real panes — blocked/working/done at a glance, detach and reattach over SSH, plus a socket API agents drive themselves.
herdr multiplexes Claude Code/Codex sessions into panes with status; CCCC replaces panes with a persistent group chat and message routing between agents.
| cccc | herdr | |
|---|---|---|
| Stars | 1.2k | 39k |
| Forks | 110 | 3.0k |
| Language | Rust | Rust |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | yesterday | 2 days ago |
| Topics | orchestration, coding | coding, orchestration |
| Curated connections | 6 | 7 |
cccc — the curator's take
Reach for CCCC when the problem is *coordination* between several long-running agents - who owns a task, whether a message was actually delivered/read, what survives a daemon restart - and you want to supervise from a phone via Telegram/Mattermost. The ledger + delivery/read/reply facts are the real differentiator; most multiplexers just tile terminals. Not for a single agent in one repo (herdr or plain tmux is lighter), and not a workflow engine: it doesn't compile plans or DAGs, it routes messages between a foreman and peers. Rust binary, pip-installable, no broker/DB/Docker - but it is a daemon that owns state, so expect one more always-on process.
herdr — the curator's take
tmux, rebuilt for the agent era: real terminal views (not wrapped reinterpretations), sessions that survive restarts and reattach over SSH, prefix keys AND mouse both first-class. The differentiator is the socket API — agents can spawn panes, read each other's output and wait on each other, which turns the multiplexer itself into coordination infrastructure, and the plugin marketplace suggests real ecosystem ambition. NOT an orchestrator: no task queues, no verification gates, no workflow graphs — it multiplexes and observes, you still decide. If you've already shaped your life around tmux, the marginal win is the agent-state awareness; weigh the switching cost honestly.