4 ms·

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

patriceckhart 20d ago
True. The features arent groundbreaking. But fair question. If tmux already fits your workflow, there may be no reason to switch. hrdx is more opinionated around running multiple coding agents across projects: it provides a workspace and pane sidebar, agent activity and completion status, built-in launch/resume flows, persistent sessions and layouts, and an external control API. The tradeoff is that it is much younger and less configurable than tmux. Try it, play around with it, love it or hate it :-)
nzoschke 20d ago
zmx, another multiplexer, has a good argument for this: https://bower.sh/you-might-not-need-tmux https://bower.sh/you-might-not-need-tmux
- platesmead 20d ago
  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.
  - patriceckhart 20d ago
    [dead]
donquichotte 20d ago
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.
- ramraj07 20d ago
  No idea what your problem is but this is categorically false. CC broke tmux when they briefly tried to open subagents inside their own tmux sessions but they've since resolved it. But they do take over the mouse mode I think.
- whalesalad 20d ago
  cc works fine for me in tmux. there is also the `/tui` command that will change the behavior of the harness from one that intercepts scrolling etc (they call this fullscreen) and the default. I run mine in default mode.
- patriceckhart 20d ago
  I wrote a blog post about my odyssey: https://www.patriceckhart.com/blog/posts/2026-08-01/hrdx https://www.patriceckhart.com/blog/posts/2026-08-01/hrdx

patriceckhart 20d ago

True. The features arent groundbreaking. But fair question. If tmux already fits your workflow, there may be no reason to switch. hrdx is more opinionated around running multiple coding agents across projects: it provides a workspace and pane sidebar, agent activity and completion status, built-in launch/resume flows, persistent sessions and layouts, and an external control API. The tradeoff is that it is much younger and less configurable than tmux. Try it, play around with it, love it or hate it :-)

nzoschke 20d ago

zmx, another multiplexer, has a good argument for this: https://bower.sh/you-might-not-need-tmux https://bower.sh/you-might-not-need-tmux

platesmead 20d ago
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.
- patriceckhart 20d ago
  [dead]

donquichotte 20d ago

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.

ramraj07 20d ago
No idea what your problem is but this is categorically false. CC broke tmux when they briefly tried to open subagents inside their own tmux sessions but they've since resolved it. But they do take over the mouse mode I think.
whalesalad 20d ago
cc works fine for me in tmux. there is also the `/tui` command that will change the behavior of the harness from one that intercepts scrolling etc (they call this fullscreen) and the default. I run mine in default mode.
patriceckhart 20d ago
I wrote a blog post about my odyssey: https://www.patriceckhart.com/blog/posts/2026-08-01/hrdx https://www.patriceckhart.com/blog/posts/2026-08-01/hrdx