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?
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.
If you do Claude remote control plus Claude app/site you get all of that though...scratches head.
True, but tmux is very configurable
https://github.com/hiroppy/tmux-agent-sidebar
Has been pretty nice