It's all about agentic work. Tmux doesn't know what an Agent is. You use Pi, you use CC, you use Codex, ... they all have primary supports in Herdr with built-in integrations around each of these harnesses

But if you don't do any agentic work, Herdr has 0 value vs. tmux.

From someone who also used screen and tmux for 30 years: 3 reasons why I switched to herder. They may not be relevant to you and in that case tmux is just great. One: visual indication which agent is working and which is waiting for an input. Two: native support for remote herdr sessions - in the same view. Three: it’s responsive and can be completely touch-driven through menus on a small iOS screen in Termius.

The point about libghostty is that Herdr doesn't try to reimplement shell forwarding or emulation, instead it uses the same code your terminal already does. This avoids compatibility problems with more complex TUIs.

Running `herdr` always opens the same session, the app is a just a UI for a server running in the background. But there is no reason to open it in multiple windows, the point is to manage all shells from inside it.

Then you can from another machine do `herdr --remote xxx.local` (over Tailscale) to access the same session, or use `herdr machine add` to get your shells from all machines at once - I don't really use this part.