Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK
Rmux, a new terminal multiplexer written in Rust, aims to leapfrog tmux and Zellij by offering a programmable layer with a Playwright-style SDK. It promises native Windows support and enhanced automation capabilities, appealing to developers seeking more robust terminal control. This "multiplexer of multiplexers" sparks debate on its true innovation and necessity amidst well-established alternatives.
The Lowdown
Rmux is a newly launched terminal multiplexer built in Rust, aiming to overcome the limitations of traditional tools like tmux by introducing a powerful programmable SDK for terminal automation. The creator, shideneyu, designed Rmux to allow for more sophisticated, code-driven interactions with terminal applications, moving beyond manual scraping and send-keys scripts.
- Rust-powered Core: Rebuilt from scratch in Rust, offering performance and modern development practices.
- Tmux-compatible: Provides a CLI with approximately 90 tmux-compatible commands, ensuring a familiar experience for existing users.
- Programmable SDK: Features a typed async Rust SDK that enables Playwright-style automation for terminals, including stable pane IDs, structured snapshots, and locator-style waits.
- Cross-Platform Native Support: Supports Linux, macOS, and Windows natively, utilizing ConPTY on Windows without requiring WSL.
- Use Cases: Designed for agents, headless CLI workflows, and human interaction, facilitating tasks like acceptance/integration testing for TUIs.
- Architectural Flexibility: Presents itself as a "multiplexer engine" that can be used to build other multiplexers, with a demo showing a mini-Zellij implementation.
- Developer Focus:
#[forbid(unsafe_code)]in upper-level crates emphasizes safety.
Rmux positions itself as a next-generation terminal multiplexer, blending the familiarity of tmux with modern programming interfaces and broad platform support. Its focus on automation and programmatic control offers a fresh perspective on interacting with terminal environments.
The Gossip
Multiplexer Musings: Comparing Rmux to Rivals
A primary discussion point revolves around how Rmux differentiates itself from established terminal multiplexers like tmux and Zellij. While some argue that many Rmux features are already achievable with existing tools, the author highlights native Windows support, superior speed, an asynchronous programmable SDK, and its design as a foundational "multiplexer engine" as key advantages. The debate touches on whether the enhanced automation capabilities justify a switch from battle-tested alternatives.
Website Woes and AI Accusations
Several commenters expressed skepticism about the Rmux project based on its website, alleging it was heavily AI-generated or featured distracting design elements like parallax scrolling. One user even questioned the accuracy of claims about tmux's programming language. The author openly acknowledged using AI for visual assets and swiftly corrected the factual error, while also defending the overall utility of the landing page in conveying information and requesting constructive feedback for improvement.
Automating Agents and CLI Control
A significant portion of the discussion centered on Rmux's potential to facilitate advanced automation and "agentic" workflows, especially via its programmable SDK. Users shared their current struggles with managing multiple panes and orchestrating CLI tools programmatically, envisioning a future where terminal applications can be driven entirely by code. The author's promise of async "wait until" functionality and the ability to build custom multiplexers resonated with those seeking deeper, more reliable terminal automation.