Comment by stingraycharles
2 hours ago
But I’m already using ghostty. I installed herdr but made the mistake of launching it from within tmux and had no idea how to close it.
I then opened it somewhere else, but I had no idea how to interact with it. I also couldn’t get two other windows to “join” the same herdr session, so I gave up and went back to tmux.
For someone who has used screen / tmux for almost 30 years at this point, what does herdr do that tmux can’t?
I use Claude Code extensively. I also use plannotator extensively, which is how I found out about it.
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.
I use Claude Code extensively as I mentioned, but what does “primary support” look like? Why should tmux “know” what an agent is?
I just use tmux with multiple ghostty sessions and I have different Claude code sessions behind different tabs and panes and work like that.
What am I missing out on that justifies now using a normal terminal+tmux anymore?
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.