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

81–90 of 97 posts

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

#82

Post by yoanwaidev »

Atotalnoob wrote: post #66

I 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.

[dead]

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

#83

Post by yoanwaidev »

igor_nast wrote: post #9

Nice, but I love my agentic IDE app. I prefer normal gui over terminal. Good luck!

To be clear on the GUI point, since my last reply here answered a different question: this is a terminal tool and it won't convert you. The reason I stay in one is that the agents already live in terminals, so the manager is a view over what's running rather than a second place things live.

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

#84

Post by 0x008 »

dhruvmittal wrote: post #26
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 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.

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

#86

Post by sebderhy »

vladgur wrote: post #64

As 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

I used exactly this setup before (mosh + tmux + Tailscale + VPS), so maybe I can help. Both tools are terminal UIs, so they fit naturally in what you have: you run them inside tmux on the VPS, and mosh handles the bad connection like it does for everything else. But honestly they don't change much when the connection is bad, because the UI still goes through the connection. This is one of the reasons I built ShellTeam (github.com/sebderhy/shellteam): the sessions stay on the VPS and the UI is a web app, so when I lose internet on a train I just reload the page and everything is still there. I'm obviously biased, but for intermittent connections I think a web UI works better than a TUI over mosh.

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

#87

Post by renezander030 »

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…

[flagged]

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

#88

Post by ThomasSchijf »

ymir_e wrote: post #71
Arthurian wrote: post #65

Earlier quoted context omitted.

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

You're spot on here. If you're truly multi-tasking with this type of setup it feels more like "tiktok coding", "brainrot coding", or any other term that should be used for it. I'm pretty sure we're moving away from it, the agent you interact with via voice or typing will go to a higher and higher abstraction level, and you won't have to effectively micro-manage them.

[flagged]
Post reply on HN