Herdr: What Multiple Machines and Multiple Agents Actually Look Like on Screen, and the Five Places I Could Put It
In Lex Fridman #501 DHH says he replaced tmux with Herdr. The reason was not that it looks nicer. It was that he had started running agents on four or five machines, and tmux has no idea what is happening inside each pane. This page covers Herdr properly. It works out whether each pane is running, blocked waiting on you, done, or idle, and it marks that state in the sidebar. The part people get wrong is how multiple machines are displayed, so that gets its own section. The answer is that every machine runs its own server, there is no single combined view of all three, and going across machines is an SSH thin client that connects to one machine at a time. DHH's setup uses GL.iNet Comet KVMs plus Tailscale to turn machines scattered across Malibu and Copenhagen into one local network, four to five machines, about three agents each, roughly sixteen threads. The second half is my own assessment. Herdr happens to fill the one empty cell in my harness table, which is observability, and the five places I could put it are a two pane setup with Claude Code writing and Codex reviewing, one workspace per project for three projects, SSH reattach to NanoClaw on the Raspberry Pi, letting an agent use the socket API to wait for another agent to get blocked, and the old Omarchy machine at the hospital. It ends with three reasons not to rush.
