Comment by stingraycharles

lol at the other replies waffling at you without describing the things that makes herdr appealing:

* agentic inbox [see which agents are waiting for your input/working/idle etc] * agents can read, spawn, send-input etc other herdr panes * makes cross harness orchestration / communication easier

fwiw I liked herdr initially but bounced after like a week because ghostty + notifications + harness extensions gave me enough that it wasnt worth learning the new thing.

If tmux can know what an agent is, it can be leveraged to communicate with an instance of that agent (input and output) given it owns the PTY, and that terminal output can be structured somehow.

If it can communicate with the agent, it can be used to drive the agent - to send it tasks, and communicate the status of those tasks.

And so Herdr - and Superlogical, and others, is a tool which leverages PTY ownership and terminal protocols to allow orchestration of coding agents across vendors using their CLI surfaces.

overall not so much, but basically if inside tmux you have 100 terminals opened and only 10 of those has 'agents' it will allow you switch quickly between those 10 terminals without spending too much time on locating those. also it will show statuses about agents, is it work done already and you may need to check it and stuff like this.