Hacker News Reader

Comment by WinstonSmith84 | Hacker News Reader

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.

View on HN

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.

part of the point is so you don’t need to stick with claude/anthropic apps? you can use other models i’m assuming

I would assume other models have their own harnesses as well but I guess if you want it at all in one place that would make sense. I just need a single model.

This is more like a harness for harnesses imo? or a managing interface. some have their own

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.

But Claude Code and Codex and the rest of tui harnesses are also very good at just typing in each other's panes basically when I need to send a message over. It's been working for almost a year now. I have been more intrigued by T3 code or something similar, just to be able for harnesses to message across machines.

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.

True, but tmux is very configurable

https://github.com/hiroppy/tmux-agent-sidebar

Has been pretty nice

How to properly secure it?

If you put it in a sandbox than herdr can no longer see it, can it?

Reply on news.ycombinator.com