Shameless plug for my project, which is a bit different.
I had the problem of crashing terminals due to OOM kills and wanted to switch to a more lightweight terminal. Also I had too many of them and couldn't find the right one any more.
I thought, why not build one yourself. The result:
It has GTK tabbed, (almost) transparently tmux-backed terminals (so quitting or crashing the app and starting it up again restores the state) in colored, named groups.
I recently added Wayland app embedding to run Chrome side by side with the terminal, local to each group, but this is still a bit shaky.
Would be nice if someone would test drive it and give me some feedback. :)
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 want to.
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 like Claude Code and OpenCode into an integrated work environment.
I have been hacking on my own Emacs based agentic coding and work environment (so much fun!) but my recent experience with Herdr has been much more productive.
Anyway, the docs for agent-manager look good, I look forward to reading HNer’s experience with it.
Claude 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
These types of responses are always so low value, they should be auto filtered out. How is Claude Code different than Codex, how is x different from y, etc. Read the repo and figure it our for yourself, good grief.
At that point this who submission should be auto filtered out since there are dozen of these and they are barely distinguishable except for couple of opinioned choices.
Because of the way humans learn, and everyone’s reference point being different (e.g. I know this, I don’t know that), this is very valuable if the author can provide a good explanation. That’s why there are books/docs like “rust for rubyists” and similar. I love finding these explanations later. Not everything needs to be researched yourself if you can get a clear/concise answer from the person trying to share/excite/get feedback on their project.
also - not everything needs to be unique. I think that is a leftover of some VC mind washing "you need a moat!". Many things can be great, and do somewhat similar things.
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/
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.
I’ve been working on something like this for a few years. Literally.
And I’ve noticed that my hobby project went from being a niche toy to something everyone was independently building almost overnight. My guess is that AI now makes it trivial for people to get started.
In any case, I since decided it would be better to focus on building my tool for myself rather than releasing it, like I was originally planning to do.
I had the problem of crashing terminals due to OOM kills and wanted to switch to a more lightweight terminal. Also I had too many of them and couldn't find the right one any more.
I thought, why not build one yourself. The result:
https://github.com/ThePixelPilgrim/kabelsalat
It has GTK tabbed, (almost) transparently tmux-backed terminals (so quitting or crashing the app and starting it up again restores the state) in colored, named groups.
I recently added Wayland app embedding to run Chrome side by side with the terminal, local to each group, but this is still a bit shaky.
Would be nice if someone would test drive it and give me some feedback. :)
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 want to.
https://github.com/herdrdev/herdr
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 like Claude Code and OpenCode into an integrated work environment.
I have been hacking on my own Emacs based agentic coding and work environment (so much fun!) but my recent experience with Herdr has been much more productive.
Anyway, the docs for agent-manager look good, I look forward to reading HNer’s experience with it.
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
And I’ve noticed that my hobby project went from being a niche toy to something everyone was independently building almost overnight. My guess is that AI now makes it trivial for people to get started.
In any case, I since decided it would be better to focus on building my tool for myself rather than releasing it, like I was originally planning to do.