Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

github.com

Post reply on HN
Print view View original

31–40 of 97 posts

Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

#31

Post by skinfaxi »

hamaluik wrote: post #21

There seem to be a lot of these sorts of tools popping up but it’s not clear to me the added value they bring in over using plain tmux (or any other “normal” session multiplexer). Can someone who uses one of these agent-specific multiplexers share their experience and reasoning for reaching for / building these? What makes this better than a normal multiplexer? I am asking in earnest; I just don’t understand but I wa…

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

Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

#33

Post by kstenerud »

hamaluik wrote: post #21

There seem to be a lot of these sorts of tools popping up but it’s not clear to me the added value they bring in over using plain tmux (or any other “normal” session multiplexer). Can someone who uses one of these agent-specific multiplexers share their experience and reasoning for reaching for / building these? What makes this better than a normal multiplexer? I am asking in earnest; I just don’t understand but I wa…

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.

Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

#34

Post by lakardion »

urnicus wrote: post #27
mark_l_watson wrote: post #6

This looks really good, but for me the timing of seeing agent-manager is bad: I read about the similar Herdr on HN several days ago and I have completely changed my dev setup for the better. I have always been a traditional simple command line tool kind of developer (I am an old man, old habbits die hard!) but I recommend at least a one day experiment with tools like agent-manager and/or Herdr that integrate tools li…

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 so! I'm quite happy with how it works. I'm using it with Ghostty and it works flawlessly. I have OOM from time to time but that is just me doing too many things. Never had I had any UI issues with it, and the UI showing the current agent status separately from the workspaces themselves is really useful

Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

#35

Post by rob »

pistoriusp wrote: post #14
skeledrew wrote: post #10

Finding it a bit wild that I've been working on something somewhat similar for a few weeks now.

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

As the great Nas once rapped:

    No idea's original, there's nothing new under the sun
    It's never what you do, but how it's done

Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

#38

Post by darcyparker »

aghuang wrote: post #11

How does this compare to something like herdr which does all of this? https://github.com/herdrdev/herdr

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.

Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

#39

Post by petesergeant »

mkl wrote: post #23
petesergeant wrote: post #15

“How does this differ from”… For all of these tools, now, there are many. After I built my own agent sandboxer[0] I went so far as to create a site dedicated to 36 other similar projects / approaches: https://pleasedonotescape.com/ 0: https://github.com/pjlsergeant/byre

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.

But that would reflect poorly on my own project ;-) More seriously you're absolutely right, I'll see if I can find some time this weekend to get that done

Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

#40

Post by petesergeant »

ymir_e wrote: post #28
hamaluik wrote: post #21

There seem to be a lot of these sorts of tools popping up but it’s not clear to me the added value they bring in over using plain tmux (or any other “normal” session multiplexer). Can someone who uses one of these agent-specific multiplexers share their experience and reasoning for reaching for / building these? What makes this better than a normal multiplexer? I am asking in earnest; I just don’t understand but I wa…

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. Tm…

This looks nice, but I think a screenshot or three in the README would help bring it to life better
Post reply on HN