← Back to context

Comment by WinstonSmith84

4 hours ago

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.

6 comments

WinstonSmith84

Reply
stingraycharles  3 hours ago

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?

  • threecheese  2 hours ago

    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.

  • strobe  3 hours ago

    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.