1. AI‑generated polish is accepted but still scrutinised
“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.” – shideneyu
“I genuinely loved your landing page… it’s obviously AI assisted but I interpreted it as a nod to itself on that and really appreciated it.” – powvans
The community notices the AI‑assisted aesthetic (the “pulsing green dot”, the blue crab) and reacts with both skepticism and appreciation, but they care more about the underlying effort and functionality than the method of creation.
2. Technical merits & design choices set RMux apart
“rmux is much faster than tmux or zellij, I did some internal benchmark and it’s promising.” – shideneyu
“You can rewrite Zellij entirely with rmux; it’s an engine, not just a front‑end.” – shideneyu
“I thought I was too zealous… separating responsibilities for session and window management would have diverged too much from tmux.” – shideneyu
These points highlight speed, an async‑wait SDK, window‑level programmability, and the decision to stay close to tmux’s API while adding Windows support and a Rust‑native engine.
3. Need for programmable multiplexers driven by agents/AI> “The Playwright‑style snapshot/wait layer is the interesting part to me… stable pane IDs plus explicit waits should make replay and debugging much saner.” – eddyaipt
“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).” – shideneyu
“Windows support, and the SDK. native async ‘wait until’ something appears on your terminal, so you don’t spam send‑keys.” – shideneyu
The discussion converges on a growing demand for a terminal multiplexer that can be driven by scripts and AI agents, with stable identifiers and async coordination as the key differentiators.