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

RMUX has launched version 0.2.0 of its new terminal multiplexer, a Rust-based tool compatible with tmux commands that offers programmable SDKs, persistent sessions, and native OS integrations. This release marks the first public preview, with all 90 tmux commands implemented, though bugs are expected.

RMUX is designed to address limitations in traditional terminal multiplexers like tmux by providing a highly scriptable, inspectable, and detachable environment suitable for long-running agents and automation workflows. The tool supports Linux, macOS, and Windows (including Windows Named Pipes), and does not require WSL. Its architecture includes a daemon, CLI, SDK, and a Ratatui widget for terminal UI rendering, all sharing a unified local protocol.

The latest release, v0.2.0, includes full implementation of tmux-compatible commands, with ongoing bug fixes. Users can install via prebuilt binaries or Cargo, and the project emphasizes security and platform neutrality with strict code safety measures. Documentation covers CLI, SDK, and API usage, with examples for scripting and automation.

Why It Matters

This development is significant because it introduces a modern, Rust-based alternative to traditional terminal multiplexers, with a focus on programmability and extensibility. RMUX’s SDK allows developers to script, inspect, and control terminal sessions programmatically, enabling new workflows for automation, remote agent management, and terminal UI customization. Its cross-platform support and native transport layers position it as a versatile tool for both individual users and enterprise environments.

Background

Terminal multiplexers like tmux have been foundational tools for developers and sysadmins, but their scripting and inspection capabilities have been limited. RMUX’s approach, announced in May 2026, seeks to modernize this space by providing a native Rust implementation with a structured SDK, persistent sessions, and a daemon architecture. The project is in early preview, with ongoing development and community feedback encouraged.

“Our goal was to rebuild the terminal multiplexer from scratch, focusing on scriptability, inspection, and long-lived agent support, all in Rust.”

— RMUX developer

“The SDK and daemon architecture could significantly change how automation and remote management are handled in terminal workflows.”

— Hacker News commenter

What Remains Unclear

It is not yet clear how stable or feature-complete RMUX will become in subsequent releases. As a fresh preview, bugs and missing features are expected, and user feedback is still accumulating. Long-term adoption depends on community engagement and further development.

What’s Next

Developers anticipate ongoing updates addressing bugs, expanding SDK capabilities, and improving platform support. Future milestones may include more advanced session management, plugin support, and broader integration with automation tools. Community feedback will likely shape subsequent releases.

Key Questions

How does RMUX compare to tmux?

RMUX is fully compatible with tmux commands and offers additional programmability via its SDK, with native support for scripting, inspection, and long-lived sessions, all built in Rust.

Can RMUX run on Windows?

Yes, RMUX supports Windows, including native Windows ConPTY and Named Pipes, without requiring WSL.

Is RMUX stable enough for production use?

As of version 0.2.0, RMUX is in early preview with bugs expected. It is suitable for testing and development, but production deployment should await further stabilization.

How can I contribute or provide feedback?

Users can report issues or contribute via the project’s GitHub repository, with documentation available at rmux.io/docs.

Source: Hacker News