RMUX

RMUX is a Rust terminal multiplexer for developers who want persistent local sessions and programmatic control of terminal work. It is most compelling for people building scripts or tools around shells, with browser sharing as an optional extra. Its free, open-source model is attractive, but remote collaboration takes deliberate setup.

Overview

RMUX keeps shells on the user's machine under a local daemon, with sessions that persist through detach and reattach. Version 0.10.0 offers a 90-command tmux-compatible surface, so users familiar with tmux workflows have a substantial starting point. The local-first design suits personal machines and self-hosted setups, but it is not a hosted terminal service.

Control uses local IPC by default. Browser sharing requires explicitly starting Web Share, and remote access additionally needs a tunnel or ingress. That opt-in boundary is useful for users who want to keep network exposure intentional; it also puts the burden of configuring remote access on them.

Key features

SDK automation

Official Rust, Python, and TypeScript SDKs provide typed session, window, and pane handles. They can send keyboard and mouse input, wait for output, capture structured snapshots, and subscribe to pane events. These tools make RMUX a stronger fit for automation that needs to observe and interact with terminal work than a multiplexer used only to manage shells. Python and TypeScript projects must install the RMUX binary first, an extra prerequisite for those workflows.

Browser sharing and security

Web Share creates browser links to a pane or session with read-write operator and read-only spectator roles. Pairing PINs are separate by default. Shells and PTYs remain on the local daemon while the browser decrypts encrypted terminal frames locally; the maker says tunnels can see handshake metadata and encrypted frames, but not keystrokes, PINs, raw tokens, or terminal cells. Per-connection keys use X25519, ML-KEM-768, and HKDF-SHA256, with terminal frames encrypted using ChaCha20-Poly1305. This architecture supports sharing without moving the shell to a hosted service, though users still need to start Web Share and arrange remote connectivity. Tailscale access, public SSH tunnel presets, and user-provided ingress URLs are supported. The Web Share frontend can also be built and served from a user's own domain.

Integrations and installation

The project documents a ratatui integration widget and a Claude Code teammate mode that runs Claude inside a local RMUX workspace. Installation options include package managers, prebuilt installers, and Cargo; quick installers verify SHA256. Chocolatey availability is in transition: version 0.10.0 was awaiting review while 0.9.1 remained available.

Pricing

RMUX is free: the RMUX plan costs nothing and is dual-licensed under MIT or Apache-2.0. There are no paid tiers or seat or quota limits described in the plan. That makes it a straightforward option for users comfortable running local software, rather than paying for hosted convenience. The project is open source, and its homepage describes the same dual license.

Platforms

RMUX supports Linux, macOS, Windows, a local CLI, and browser access through Web Share. Rust, Python, and TypeScript SDKs are available; Python and TypeScript require the RMUX binary to be installed first. Browser access is for sharing panes or sessions, not a replacement for the local daemon.

Who it's for

RMUX is best for developers who want persistent local shells and need code to drive, inspect, or coordinate terminal activity. It also suits self-hosters who want optional browser collaboration with operator and spectator roles while keeping shells local. It is a weaker fit for anyone seeking a managed hosted service, or who wants remote access without configuring a tunnel or ingress.

Pros and cons

• Pros: Persistent local sessions and a 90-command tmux-compatible surface make it practical for established multiplexer workflows.
• Pros: Typed SDKs, structured snapshots, input controls, waits, and pane events support automation beyond basic shell launching.
• Pros: Web Share offers separate operator and spectator roles, PIN pairing by default, and encrypted browser sharing while shells stay local.
• Pros: Free use, open-source licensing, and self-hosting options give users control over deployment and cost.
• Cons: Remote access needs Web Share plus a tunnel or ingress, so collaboration is not turnkey.
• Cons: Python and TypeScript SDKs depend on installing the RMUX binary, adding setup to those projects.
• Cons: The project documents no plugins or extensions, limiting users who specifically need an extension system.

Alternatives

Zellij is worth considering if you want free, open-source software with no account required, or want to evaluate its separate hosted session-sharing option, Zellij.online, which has a free tier and is in closed beta.

muxterm may suit users looking for a free, MIT-licensed, self-hosted multiplexer distributed as a single binary. Okena is another free option, with a wider platform range that includes Android and iOS. muxel offers free GPL-3.0 software for Linux, macOS, and Windows, while openmux is free MIT-licensed software for macOS Apple Silicon and Linux x64 or arm64. p2pmux is a free MIT-licensed alternative for Linux and macOS. Quil is free, with no paid tier or hosted version. Herdr is free Apache 2.0 software that runs locally on macOS, Linux, and Windows.

Browse more options in Terminal Multiplexers.

Verdict

Choose RMUX if you want free local persistence paired with SDKs that can actively automate and observe terminal sessions. Its strongest distinction is bringing that automation together with opt-in, encrypted browser sharing while leaving shells on your machine. Look elsewhere if you need hosted collaboration without configuring remote access, or if the required binary setup for Python and TypeScript SDKs does not suit your workflow.