- I get OS level notifications when the agent is ready.

- I don't need to use TMUX's wonky keyboard shortcuts

- I moved off of TMUX anyway, when ssh-ing into remote servers became 'not a thing'

- automatic coding session management, like auto resume, layout manamgement, etc. out of the box, without setting up TMUX, which could be a wormhole for some, by the time you fix mouse scrolling, cut/paste, etc...

I'm currently using CMUX, and been pretty happy with it it at this time, but loving the evolution of all these tools

I've tested out just about every tool like this, and ended up coding my own, it is really minimal though.

The primary reason people reach for these tools are two to three reasons:

1. Tmux does not natively show agent statuses of agents / notify you when one needs input. Helpful when you have a huge list of small things to fix: I just spin up N agents in parallel to handle all of them, then I go over and review.

2. Tmux does not handle worktree handling. If you wanna make changes in parallel you cannot have two agents make db migrations at the same time. The way to solve for this is to have them work on two different worktrees with separate environments, ports etc.

3. Tmux tree view is not super beautiful, especially for viewing agents.

I built this as a tmux plugin since I don't really want to opt-out of tmux as a whole, especially since I like my keybindings there.

https://github.com/Ymirke/tmux-agent-switcher

I’ve been using herdr lately and before that I was using zellij and before that tmux and before that gnu screen

For me the main advantage of herdr is that when I have the codex integration activated, herdr will keep track of the codex session ids and automatically restore them after restart

With the other multiplexers I had to create a separate tool that would save/restore layout/tabs/panes/session ids. And I had to run it manually. With herdr it just works, almost out of the box

Oh, it’s also very nice that you can create groups of tabs, so it’s easier to organize if you have more than 3-4 terminal sessions open (I usually keep at least 3 tabs, each split into an agent pane and a zsh pane)

And lastly, mouse scroll support is a lot better. I’ve had many issues with scrolling codex’s output. tmux and zellij’s scrolling wouldn’t play nicely with codex’s output, but herdr seems to work very well

I've been using herdr for a couple of weeks. The only real advantage is that it makes the agent status glanceable in the sidebar, which can be nice if you don't want to cycle through your tmux panes to check if something's blocked or complete. Other than that, it's kind of just tmux (which is nice, I like tmux).

I built yoloAI, which is a sandboxer so it uses tmux to keep the agent alive inside. Since I can just reattach to them or use VS code tunnels, I don't really have a need for a multiplexer, though.

My main reason for herdr over tmux is the priority queue of agents requiring intervention.

I tried herdr recently, and I missed many tmux features I really liked.

tmux has a better `prefix-[` mode where you 1) can do visual selection using line/block mode 2) you can use `o` to switch to other side (just like vim) 3) it pauses/freezes the state of the output so you have time to capture

In herdr, its very basic and incomplete if you're a vim/nvim/tmux power user. And if you're in a TUI that shows some text and then hides it, its hard to do the selection in herdr before it disappears.

To give herdr credit, I did like it's `prefix-e` which opens the history in vim so you can you real selection utils.

As I was looking at herdr, I found there many other solutions that were like it built on the more robust tmux. I am still evaluating, but there are plenty of solutions that have hooks to observe what's going on in agents in other panes/windows like herdr.

I like the Primeagen's `tmux sessionizer` style solutions for nvim to work with git worktrees that each agent may be in. And I like the tmux-agent-sidebar.

yes exactly my thought. They're quite the same, a feature more a feature less

Thanks for sharing your experience with Herdr! I've been considering taking the plunge for a few weeks - going to do a one day experiment today.

Do you know how does Herdr compare to native “claude agents” view?

yes but if you don't create a company you can't get funding.

Normal GUI runs local. I have mosh running from Blink on my iPhone to my server and I can continue months long session of AI

These types of responses are always so low value, they should be auto filtered out. How is Claude Code different than Codex, how is x different from y, etc. Read the repo and figure it our for yourself, good grief.

OPs tool is not a sandboxer and isn’t like the other projects in your list. OP is an agent multiplexer, of which there also are many similar projects, but not a sandboxer.

This is great! It would be really helpful if it had some measure of the number of users (stars?) and a contributor count. It's pretty hard to determine which of these projects are going to stick around. Total length of time under active development and percentage of code committed by agents would also be informative.

I had the same experience, but someone calmed me down by saying "we're all working on solving this problem."

I'm seeing a lot of this across all sorts of apps right now. We're at a sort of cambrian explosion point for software.

I too built my own equivalent of this (belfry.robgough.net). I take it as a good thing, we're all using these tools and coming to similar conclusions.

I suspect over time it'll settle down, once we've gotten comfortable with the new ways of working and found the new normal.

I’ve been working on something like this for a few years. Literally.

And I’ve noticed that my hobby project went from being a niche toy to something everyone was independently building almost overnight. My guess is that AI now makes it trivial for people to get started.

In any case, I since decided it would be better to focus on building my tool for myself rather than releasing it, like I was originally planning to do.