Live data from Hacker News

Herdr: Agent multiplexer that lives in your terminal

github.com

71–80 of 115 posts

Re: Herdr: Agent multiplexer that lives in your terminal

#71

Will people really need a bunch of different agents? Even using two codex session for different project make me feel a bit overwhelmed, or may be i just old

Maybe not when answers will be almost instant, but the biggest gap to me now is latency, not capability. Having to wait for 5 minutes and more for an answer, I can switch to another project / feature / etc. and run work streams in parallel.

Dang, that's not too much context switching for your brain?

Re: Herdr: Agent multiplexer that lives in your terminal

#72
post #23

This is way to complex... Why don't just use some harness which manages all that and give u a good UI?

You might like Circus Chief. It’s a web based UI focused on mobile - local first. Supports Claude Code, Codex, and Gemini. Supports auto retries when you run out of tokens, scheduled tasks etc. It’s been great for me as I juggle a Codex, Claude Code, and z.ai subscription.

https://github.com/ferrislucas/Circus-Chief

Full disclosure: it’s my project

Re: Herdr: Agent multiplexer that lives in your terminal

#73

The utility is not obvious, but I've been using herdr for a few weeks after a friend recommended it, and it's been a great tool. I had about a dozen different terminal windows, each one with multiple tabs, which was becoming a mess to manage; multiple agents and harnesses running that I could only inspect by remote access/VNC away from home. With this, I can keep things more organized (project workspaces, tabs), beca…

Couldn't you just use tmux for the remote access?

Re: Herdr: Agent multiplexer that lives in your terminal

#75
post #6

Just use tmux no?

How would you know if a tab that isn't frontmost is waiting for input or complete or whatever?

I added sounds: https://github.com/gpurkins/waiting-for-claudot which has become a bit pavlovian. This along with notifications in iTerm is good enough to juggle some claude sessions.

Re: Herdr: Agent multiplexer that lives in your terminal

#76

Will people really need a bunch of different agents? Even using two codex session for different project make me feel a bit overwhelmed, or may be i just old

If you have more than one issue to work on, then you can open an agent for each one and go though them round-robin.

Maybe very early on a greenfield project you only have one known issue (the next feature you're building), but other than that seems like short-changing yourself.

Re: Herdr: Agent multiplexer that lives in your terminal

#78
I've been using this and it's been really nice for a specific use case: running agents locally alongside agents in a remote sandbox environment. Most apps managing this split seem to want to manage your sandbox for you, but we've already built out some nice tooling and infrastructure for that that meets our needs. I don't want to add a new vendor in the mix for our infra that may not exist in a year and that will be harder to integrate with. Combined with some additional tooling I made, herdr lets me easily connect to remote agent sessions, see their status in the sidebar and fluidly switch back to work on my local machine from one interface.

Re: Herdr: Agent multiplexer that lives in your terminal

#80

Once you get it set up, Emacs is a pretty damn good "agent" multiplexer as well. I use agent-shell with Projectile on Doom Emacs as my main workflow these days, and it works very well even if I have 6 projects open or whatever. Claude and Codex are also both quite good at working with Emacs as well. Depending on your isolation/sandboxing strategy, they can either run commands against your session via emacsclient (a b…

If you like scary, there are also emacs based agents like gptel which support tools like "eval-elisp".

A kitchen sink is almost indistinguishable from a sandbox, right?

... right?

Post reply on HN