Hacker News new | ask | show | jobs
Herdr: Agent multiplexer that lives in your terminal (github.com)
41 points by mzehrer 3 hours ago
5 comments

nice, not dissimilar to what i built for https://github.com/storozhenko98/beehive
does it support a setup where each agent can be in a different SSH session? or must they all run in the same place.

it seems to support running a remote herdr over SSH but unclear if it can add remote agents (each agent has its own sandbox where its installed and you first SSH into it and then start the agent there)

Same question.

I usually have one local clause orchestrating multiple remote Claude in different tmux . And then another orchester and remote vm worker sin tmux for another repo etc...

It gets a bit hard to keep the overview but I don't want to give up my parallelism, your too might help

Interesting, how is this orchestration set up?
One way is to use something like https://shellbox.dev - you start new boxes and manage it all through ssh, icl agent running inside
afaik, you should be able to use named session to achieve this: https://herdr.dev/docs/persistence-remote/
Just use tmux no?
How would you know if a tab that isn't frontmost is waiting for input or complete or whatever?
Someone else suggested the bell character. But you can also just set tmux pane names or color. Which you can also do from your agent harnass.
You use an agentic harness which terminates with bell character[0]. This lights up tmux, clearly indicating that it's done.

[0]: https://en.wikipedia.org/wiki/Bell_character

Tried this for a couple days, but conductor.build is way better IME. Running _in_ the terminal is a flex, but doesn't actually bring any advantage.
Running in the terminal means I can access it via ssh on my phone (& tailscale). Do any of the other solutions let you do this?
I'm using `opencode --web`. Running over HTTP means I can use it comfortably on my phone with Tailscale.
I need a shepherd for my terminals.