Live data from Hacker News

Herdr: Agent multiplexer that lives in your terminal

github.com

51–60 of 115 posts

Re: Herdr: Agent multiplexer that lives in your terminal

#51
post #9
post #6

Earlier quoted context omitted.

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.

That's only half an answer.

Re: Herdr: Agent multiplexer that lives in your terminal

#52

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

I often have many active. Bug investigations, writing code, reviewing, checking logs after deploys and so on.

Re: Herdr: Agent multiplexer that lives in your terminal

#53
post #12

Earlier quoted context omitted.

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.

Check out paseo and similar tools to that. It has a lot of features but you'll find its mobile client is much better than opencode's web view.

Re: Herdr: Agent multiplexer that lives in your terminal

#54

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

I found that a good tool helps a lot once I switched to Github Copilot app. It solved the friction and mental tax for me. I easily manage 4 sessions in parallel on same or different projects while 2 was max in the past. The bottleneck now is only in review and decision making.

Re: Herdr: Agent multiplexer that lives in your terminal

#55

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.

Re: Herdr: Agent multiplexer that lives in your terminal

#56

How do people use terminal multiplexers together with vim? Ctrl+B is so hardwired in my fingers for scrolling back one screen that there's no way I'm remapping that one in vim itself. So then you have to remap that in your terminal multiplexer, while at the same time there's a bunch of people saying never change the leader key... Curious what vim users especially do about this?

Change the tmux leader to ctrl-space, problem fixed!

Re: Herdr: Agent multiplexer that lives in your terminal

#59
Multiplexing the agents is clearly the first obvious pain point, but the other one I keep encountering after this is visibility: with multiple agents running, it becomes difficult to see what each of them is doing, what program did they call, and where they are getting stuck until they complete or fail.

Is there any information from Herdr about what each agent is up to beyond the output? Or does it just concentrate on orchestration for the time being?

Post reply on HN