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?
Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
61–70 of 97 posts
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#62I 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?
It's useful for running multiple long running tasks alongside your "primary" work. As an example I currently have 3 tabs open running a PR review, 1 tab running "autonomous development" for a small time feature and then my "primary" window for working on a feature.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#63I decided to test herdr and orca today and I'm really impressed with both, especially orca.
I had no idea how far the ADE / multiplexer space was, I'm very excited for more progress in this space!
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#64As I was traveling by trains and planes with finicky internet I started using mosh + tmux + Tailscale + VPs to run my agents
Curious how herdr or agent-manager fits into this remote-dev with intermittent connections experience
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#65There 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…
In your experience using your plugin (and the other tools that do something similar like herdr), does it make doing a larger volume of work feel more manageable?
In my experience thus far, surfacing/managing session state is only part of the issue, context switching between them is another entirely and feels like the real productivity bottleneck for me
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#66I 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.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#67I'm going to be blunt. I don't care about any more AI tools.
No need to comment.
No, I think there is. Too many people building AI tools. I see it in my org. Tons of low value work but the ai sycophant is telling everyone "you're a genius, this is great" so they continue.
We built a "fire and forget" agent that's supposed to complete whole jira tasks or that we're supposed to be able to call from slack. You put a ticket in to "make random.md document" and it creates a ton of unit tests and makes "notrandom.md" and says "success". Tons of engineers pulling plugins/skills/etc and injecting them in places they don't belong, lots with blatantly wrong info. People making whole frameworks and tools around their AI workflows, but they're worthless, anything that made sense gets released a week after they finish building from anthropic/openai/etc.
It's ai psychosis from c-level down.
I'm tired.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#68There 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…
Most of the AI tools people are building have little to zero value.
If you're making valuable tools, anthropic, openai, or one of the other big players in the space will hire you/buy you out and then they will release the tool themselves.
I'm getting really tired of everyone doing their own special rain dances and then acting like they made it rain.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#69I'm going to be blunt. I don't care about any more AI tools.
100% agree. AI isn't hacking, it's a completely different crowd. So much front page space is wasted talking about the latest version, some funding controversy, or these useless add-on tools.
Re: Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode
#70I'm going to be blunt. I don't care about any more AI tools.
100% agree. AI isn't hacking, it's a completely different crowd. So much front page space is wasted talking about the latest version, some funding controversy, or these useless add-on tools.
And this is the shit we're seeing in public.
Can't tell you how much garbage AI tooling is being built within my org. Whole teams spinning their wheels basically rebuilding claude code because execs are obsessed with "dark factory". Individuals building plugins/skills/mcps that are duplicated or just plain wrong (why do I see so many skills/plugins telling our agents to use main branch when we've always used master???).
I've yanked MOST tools OUT of my claude code/opencode/codex. MCPs to centralize auth to our knowledge base, jira, gitlab. Then a singular short simple markdown file in each project/repo. When brainstorming, maybe I'll create a one off .md that I'll delete once the thing is built/implemented.
I'm tired.