Live data from Hacker News

Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

github.com

51–60 of 111 posts

Re: Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

#51

Scriptable terminal multiplexer? Interesting portable scripting thingy. But it would only work with portable tools, not just everything. Especially with Windows tools.

I wrote it for rust apps in mind, same usecase as for Ratatui. You’re right maybe I need to expose more tools with the cli

Re: Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

#53
post #44

Cool project, I like the idea of having tmux-compatible CLI. I used Zellij to get better UX, but many agent tools integrate with tmux. This way agent tools can still integrate tmux as a defacto standard for programmatic interface while having better interface for users. But I wonder if tmux/rmux design is suboptimal since it couples session persistence and window management together. Do you have an opinion the design…

I thought I was too zealous because I created 11 crates respecting single responsibility principles.. I would have been all in to risk it further and separating responsibilities for session and window management but it would have diverged too much from tmux. I wanted a 1-1 port for now

Re: Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

#55
Very cool! I think the hype around “agents are so good that you never actually need to see the underlying commands they are running or interact with the terminal session that they’re running” misses out on a lot of very important use cases, particularly around long running processes that may be shared across multiple agents. This will be very cool to see how best practices evolve!

Re: Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

#56
post #44

Cool project, I like the idea of having tmux-compatible CLI. I used Zellij to get better UX, but many agent tools integrate with tmux. This way agent tools can still integrate tmux as a defacto standard for programmatic interface while having better interface for users. But I wonder if tmux/rmux design is suboptimal since it couples session persistence and window management together. Do you have an opinion the design…

I thought I was too zealous because I created 11 crates respecting single responsibility principles.. I would have been all in to risk it further and separating responsibilities for session and window management but it would have diverged too much from tmux. I wanted a 1-1 port for now

Fair point, given it is more unconventional design, it is a riskier way in order to get something that works.

Re: Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

#57
post #55

Very cool! I think the hype around “agents are so good that you never actually need to see the underlying commands they are running or interact with the terminal session that they’re running” misses out on a lot of very important use cases, particularly around long running processes that may be shared across multiple agents. This will be very cool to see how best practices evolve!

Same ! TUI are becoming more and more mainstream so there is a need for automated multiplexing , not used by humans but by programs (and agents)

Re: Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

#59
post #3

The website is a little too obviously made by Claude. The first thing I noticed is the classic "pill with pulsing green dot that says something is active or live" claudism.

The video of the front page is assisted by AI, I am not a vfx artist; please check rmux code architecture instead, I put a lot of efforts on it

For what it's worth I genuinely loved your landing page. I casually clicked through and got an immediate unexpected chuckle at the giant animated crab.

It's obviously AI assisted but I interpreted it as a nod to itself on that and really appreciated it.

Re: Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

#60
post #49

Congrats on the launch. If emacs was unavailable and I needed tmux, I would try it. I am old school, and use emacs daemons for all shell multiplexing. The agents dont need explanations and know how to use emacsclient to create, read, or send inputs to named buffers that run the shells. Elisp is powerful, so manipulating windows is a breeze. Lots of people on tmux would benefit from this design though.

I didn't know you could do this with Emacs
Post reply on HN