Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
41–50 of 97 posts
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#42Isn't this what https://www.superlogical.com/ supposed to accomplish?
yes but if you don't create a company you can't get funding.
codex(or whatever they're calling the bundled desktop experience) = selling inference
claude code = selling inference
conductor = selling hosted agents
superlogical = selling... something
I recommend everyone build their own. It's fun, you'll learn a bit, and assuming you work as a software engineer the dogfooding is built in. I built ouijit as my own example of this: https://ouijit.com & https://github.com/ouijit/ouijit (note that I am not trying to make money, just free as in libre AND beer)
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#43How 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 a…
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#44There 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 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 should probably download different types of frog sounds for different agents though.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#45“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.
There are projects that have no stars that may be great and projects that have a high star count and are absolute garbage (because you can fake stars)
I tend to look at the commits, contributors, closed/open issue count ratio and the changelog.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#46“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
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#47Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#48There 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…
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
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#49There 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 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…