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)
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...
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), because it's backed by a persistent process, I can ssh into the machine, with tailscale, run herdr and see all active sessions, do some debugging and one-off prompts.
Even better, I can do that from my phone and iPad using Prompt/Termius. It gives me the best part of 'xxclaw' harnesses with none of the complexity.
Does herdr with termius on android support touch/tap operation? I tried herdr on mac, it works really great. But i tried access it via termius from my android, I can't tap/interact with it. Am i missing something?
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
Nope, they need to signal, that they know what they are doing and chic, and very trendy. And agent cnt must be > 12, open windows cnt > 6 otherwise feels himself as a peasant.
I switched from tmux to Zellij a while back, and lately added a stop hook that sends a terminal ping to the correct tab when the agent is done (and I'm not looking at the tab). It has been pretty convenient so far.
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 bit scary) or dump elisp in the REPL for you to evaluate. Both are really efficient in terms of giving you a fast feedback loop.
Hahahaha. I think for the limited purpose of iterating on elisp code, using gptel or efrit to let an agent run wild and iterate in a live environment could be useful. I'd want to run that in a VM though, and not as my user or with access to personal data beyond reusable parts of my config.
Getting a lot of flack in all these comments, I really like this tool. Have been super easy to use and scale to multiple agents. I've had a ton of issues with tmux and copy and paste, this just works. I was using warp terminal, and even working on my own fork of it with it's recent open source status, but this has won me over.
I started building my own version of this before I discovered herdr, and while its not quite the same it's improved my development workflow by an order of magnitude. https://jmux.build
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?
Have you built anything around it? I was thinking it might be useful to potentially script based on space and tab name (like create dir named tab in space) and other little QOL workflow tweaks but haven't looked into it really.
has anybody figured out how to get this to open a fixed layout? I'm using tmuxp to do this easily with tmux but would switch to this pretty quickly if it was easy to get my layout over. It's really nice. It's like zellij without the bloat (but with different ai bloat that doesn't seem to drag down performance at all and isn't in your face unless you want it in your face)
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.
52 comments
[ 4.3 ms ] story [ 86.4 ms ] threadit 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)
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?
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), because it's backed by a persistent process, I can ssh into the machine, with tailscale, run herdr and see all active sessions, do some debugging and one-off prompts.
Even better, I can do that from my phone and iPad using Prompt/Termius. It gives me the best part of 'xxclaw' harnesses with none of the complexity.
Added an example here:
https://johnny.chadda.se/zellij-stop-hook/
Does anyone know anything like this for Ghostty?
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 bit scary) or dump elisp in the REPL for you to evaluate. Both are really efficient in terms of giving you a fast feedback loop.
A kitchen sink is almost indistinguishable from a sandbox, right?
... right?
I am going to give them a try side by side!
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?
https://github.com/elij/macher-agent