I use coding agent but still don’t see the need to manage a swarm of them like this. Is there an actual use case for this or this is just for tokenmaxxing?
[deleted]
Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
91–97 of 97 posts
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#92I don’t get the point of these. Ghostty has tabs which show the icons for the terminal TUI. You can just look at those for the status. Same with windows terminal, and you can use either of those to have tiling.
[deleted]
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#93Claude comes with very nice hook-api you can use it to customise notifications and allow tmux window to blink or to come to the front when Claude needs your attention
[flagged]
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#94Earlier quoted context omitted.
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 don’t get this argument that’s soooo easy for add a window marker to tmux windows that updates with a Claude hook.
[dead]
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#95Isn't this what https://www.superlogical.com/ supposed to accomplish?
Different scope, as far as I can tell from their site: they describe a multiplexer for all work, spanning remote hosts, sandboxes, CI, production systems and shared terminals. This is a Go binary that drives tmux on the machine you're already on, and every session it creates is an ordinary tmux session you can attach to without it. Much smaller bet, and it stops where tmux stops.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#96Am I the only one who prefers a full on GUI (eg Claude Desktop)?
You're not, and this won't convert you. The reason I stay in a terminal is that the agents already live in one, so a TUI is a view over what's running rather than a second place things live. If your agent already runs in a GUI, that argument doesn't apply to you.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#97There 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 build one, an inhouse one for myself. I think it's a worth doing and see if it works for you. Especially for someone who works independently most of the time. I get it to follow and support my working style, workflow and idiosyncrasies. I started out because I wanted something that queues my work serially for each project so I can work on main and I can type what I want to do in it instead of writing to an ever-growing TODO list.
I then make it show icons and indicators for blockers, ready sessions that need attention, TODO lists that include notifications and actions (because it's so easy to miss things while working on/with many sessions). Shows costs (loop coordinator and non-LC costs, by day, etc) so I can optimize costs.
It's fun, a learning experience and it's more productive. With excellent SOTA and coding agents now, we should be building tools to improve our work even more than before. Try it.