Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
11–19 of 19 posts
Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#12I hate to be that guy, but why would I use this over tmux? All of the features and qualities noted in the readme do not feel novel or unique.
Claude Code stopped working in tmux for me at some point. Which is of course more of a CC problem than a tmux one, but maybe OP was trying to work around such issues.
Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#13Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#14I hate to be that guy, but why would I use this over tmux? All of the features and qualities noted in the readme do not feel novel or unique.
zmx, another multiplexer, has a good argument for this: https://bower.sh/you-might-not-need-tmux
hrdx looks great, but as it does it's own multiplexing, I'm not sure the post's rationale is suggesting something like hrdx.
Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#15I hate to be that guy, but why would I use this over tmux? All of the features and qualities noted in the readme do not feel novel or unique.
Claude Code stopped working in tmux for me at some point. Which is of course more of a CC problem than a tmux one, but maybe OP was trying to work around such issues.
Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#16This looks nice. But I'm curious -- you're clearly inspired by https://herdr.dev (me too) but you must have had some reason to build your own version. So what's unique or what did you want to change?
I hadn't seen herdr until just now but I built a similar tool with it's own keyboard bindings https://github.com/hadlock/cscope . Claude Code changed some underlying changes to copy-paste so it needs updating. But I think this kind of "I wish my workspace did this/had these features" is a pretty common trope. It is about $10 worth of your employer's monthly token allocation (or personal account if you pay for one) an…
Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#17Earlier quoted context omitted.
Yes, absolutely inspired by herdr. The main reason I built hrdx was that I wanted to explore the idea in Go and shape it around my own workflow. I focused on persistent PTY sessions, workspace and Git branch organization, agent activity indicators, custom agent harnesses, and a socket API for external automation. There is definitely overlap, and I'm not claiming the underlying idea is unique. It is mostly my own take…
Yeah, I've got a lot of tooling in Go and have been building some workflows on top of herdr, so a Go version of the same concept is a bit nicer to work with for me. I'll have to play with it a bit more later. Which PTY are you using?
Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#18Earlier quoted context omitted.
zmx, another multiplexer, has a good argument for this: https://bower.sh/you-might-not-need-tmux
That post advocates for passthru terminal persistence, and instead letting your host terminal/WM be the multiplexer. hrdx looks great, but as it does it's own multiplexing, I'm not sure the post's rationale is suggesting something like hrdx.
Re: Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
#19I hate to be that guy, but why would I use this over tmux? All of the features and qualities noted in the readme do not feel novel or unique.
Claude Code stopped working in tmux for me at some point. Which is of course more of a CC problem than a tmux one, but maybe OP was trying to work around such issues.