RMUX
rmux.io
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What RMUX is
RMUX is a local terminal multiplexer written in Rust. A local daemon owns its shells, and RMUX 0.10.0 offers a tmux-compatible surface of 90 commands for persistent sessions that users can detach from and reattach to. Its SDKs support automation across sessions, windows, and panes: programs can send keyboard or mouse input, wait for output, capture structured snapshots, and receive pane events. Official SDKs are available for Rust, Python, and TypeScript, although the Python and TypeScript SDKs require the RMUX binary to be installed first. Web Share creates browser links to a pane or session while the shell stays on the user’s machine. Links can allow read-write operator or read-only spectator access, with separate pairing PINs enabled by default. Sharing can use private Tailscale access, public SSH tunnel presets, or a user-provided ingress URL. The project says terminal frames are encrypted and decrypted in the browser. Default control uses local IPC; remote sharing requires starting Web Share and a tunnel or ingress. RMUX is self-hosted software, dual-licensed under MIT and Apache-2.0, and available for Linux, macOS, and Windows.
Who it suits
RMUX suits developers and technical teams who want persistent local terminal sessions or programmatic control of panes. Its browser sharing options can support remote operators and read-only viewers while shells remain on the local machine.
Good to know, and what to watch
- 90-command tmux-compatible surface
- Persistent sessions support detach and reattach
- Official Rust, Python, and TypeScript SDKs
- Operator and spectator browser links
- MIT or Apache-2.0 licensing
- Python and TypeScript SDKs require the RMUX binary
- Remote access requires starting Web Share and a tunnel or ingress
- Version 0.10.0 was awaiting Chocolatey review
Plans
Every plan and priceRMUX
Open source
Getting started
- Install RMUX with a package manager, prebuilt installer, or Cargo
- Start the local RMUX daemon and create a session
- Use the local CLI or a Rust, Python, or TypeScript SDK
- Install the RMUX binary before using the Python or TypeScript SDKs
- Start Web Share when you need a browser link
- Choose Tailscale, an SSH tunnel preset, or an ingress URL for remote access
Limits to check
Persistence is local. Python and TypeScript SDK use requires the RMUX binary, and remote browser access needs Web Share plus a tunnel or ingress.
The Club's review
RMUX is a Rust terminal multiplexer for developers who want persistent local shells and programmatic control over terminal work. It is strongest for automation and opt-in browser collaboration; it is less suited to teams seeking a hosted service with no setup to manage.
Overview
RMUX keeps shells under a local daemon, so sessions can persist through detach and reattach. Version 0.10.0 offers a tmux-compatible 90-command surface, which makes it a practical option for users who want familiar multiplexer commands alongside SDK control. Its persistence is local rather than hosted, a meaningful distinction for anyone expecting sessions to follow them through a provider-managed service.
Control defaults to local IPC. Browser sharing and remote access require starting Web Share explicitly, and remote connections also need a tunnel or ingress. That opt-in boundary is useful for keeping ordinary terminal work local, but remote collaboration requires configuration.
Key features
SDK automation
Official Rust, Python, and TypeScript SDKs provide typed session, window, and pane handles. They support keyboard and mouse input, waits for output, structured snapshots, and pane-event subscriptions. This makes RMUX more than a session manager: scripts and tools can inspect and operate terminal work. Python and TypeScript users must install the RMUX binary first, so these SDKs are not standalone dependencies.
Browser sharing
Web Share creates browser links for a pane or session while the shell and PTY remain on the local daemon. It supports read-write operator and read-only spectator access, with separate pairing PINs enabled by default. That role split suits guided troubleshooting or supervised access, though the host still needs to start sharing and arrange connectivity.
Sharing can use private Tailscale access, public SSH tunnel presets, or a user-provided ingress URL. The browser decrypts terminal frames locally; the maker says tunnels see handshake metadata and encrypted frames, not keystrokes, PINs, raw tokens, or terminal cells. The frontend can also be built and served from a user's own domain. These are substantial controls for self-hosters, but they do not remove the need to choose and configure an access path.
Integrations and installation
RMUX documents a ratatui integration widget and a Claude Code teammate mode that runs Claude inside a local workspace. Installation is available through package managers, prebuilt installers, and Cargo; quick installers verify SHA256. Windows package availability can lag: version 0.10.0 was awaiting Chocolatey review while 0.9.1 remained available there.
Pricing
RMUX is free at no cost under a dual MIT or Apache-2.0 license. The plan is self-hosted local software, with local persistence, collaboration features, and custom pane layouts; it does not include a hosted service. There are no paid tiers or usage quotas in the plan, but users take responsibility for installation and remote-access setup.
Platforms
RMUX supports Linux, macOS, and Windows, as well as a local CLI, browser access through Web Share, and Rust, Python, and TypeScript SDKs. Its API and self-hosted options suit developers and operators who want to integrate terminal work into their own workflows. The Python and TypeScript SDKs depend on the installed binary.
Who it's for
Choose RMUX if you want local persistent sessions that can be automated through typed SDKs, or need to share terminal output and control through browser links without moving the shell off your machine. It is particularly compelling for developers building terminal-driven workflows and self-hosters who can manage tunnels or ingress. Look elsewhere if you need a managed hosted session service or want remote sharing to work without setup.
Pros and cons
- Pros: Persistent local sessions and a 90-command tmux-compatible surface combine familiar terminal workflows with daemon-owned shells.
- Pros: SDKs offer structured snapshots, input, waits, and pane events, enabling automation beyond launching shells.
- Pros: Browser sharing separates operator and spectator roles and keeps shells local while encrypting terminal frames.
- Cons: Python and TypeScript SDKs require the binary, adding a system installation dependency to application projects.
- Cons: Remote sharing requires explicitly starting Web Share and configuring a tunnel or ingress; it is not a turnkey hosted collaboration product.
- Cons: The Windows Chocolatey package for 0.10.0 was still awaiting review, with 0.9.1 remaining available there.
Alternatives
For another free, open-source multiplexer, consider muxel, which supports Linux, macOS, and Windows. Zellij is a free, no-account-required option, while its Zellij.online hosted sharing has a free tier and is in closed beta; choose it if that hosted route better fits your needs. p2pmux is a free MIT-licensed alternative for Linux and macOS. muxterm is free, self-hosted, MIT-licensed, and distributed as a single binary; openmux is free and self-hosted for macOS Apple Silicon and Linux x64 or arm64. Herdr is a free Apache-licensed local runtime for macOS, Linux, and Windows. Okena is another free option. Browse Terminal Multiplexers for more choices.
Verdict
RMUX is a strong fit for developers and self-hosters who want local session persistence paired with SDK automation and carefully configurable browser sharing. Its free dual licensing and capable automation are the main reasons to choose it; the need to install the binary and configure remote access are the main reasons to look elsewhere.
The verdict
RMUX combines local persistent sessions with SDK automation and optional browser sharing. Its Python and TypeScript SDKs depend on the installed binary, and remote access requires explicit setup.
Questions people ask
Is RMUX free?
Yes. RMUX is free, open-source software under a dual MIT and Apache-2.0 license.
Which platforms can run RMUX?
RMUX supports Linux, macOS, Windows, local CLI use, browser access through Web Share, and Rust, Python, and TypeScript SDKs.
Does RMUX work with tmux?
RMUX 0.10.0 offers a tmux-compatible surface of 90 commands, with persistent sessions that can be detached and reattached.
How does browser sharing work?
Web Share creates operator or read-only spectator links while shells stay on the local machine. The browser decrypts encrypted terminal updates locally.
Can I self-host the sharing interface?
Yes. The Web Share frontend is open source and can be built and served from your own domain.
Are plugins available?
The listed product details state that plugins or extensions are not available.
What the maker publishes
- Automation
- SDK automation includes typed session, window, and pane handles, structured snapshots, keyboard and mouse input, waits, and pane events. source
- Encryption
- Web Share derives per-connection keys using X25519, ML-KEM-768, and HKDF-SHA256, then encrypts terminal frames with ChaCha20-Poly1305. source
- Installation
- Install options include package managers, prebuilt installers, and Cargo; the docs say quick installers verify SHA256. source
- Integrations
- The project documents a ratatui integration widget and a Claude Code teammate mode that runs Claude inside a local RMUX workspace. source
- License
- RMUX is dual-licensed under MIT or Apache License 2.0. source
- Licensing
- The maker's homepage says RMUX is dual-licensed under Apache-2.0 and MIT. source
- Limit
- The Python and TypeScript SDKs require the RMUX binary to be installed first. source
- Network exposure
- Default control uses local IPC, and browser sharing or remote access requires explicitly starting Web Share and, for remote access, a tunnel or ingress. source
- Package availability
- The docs say RMUX 0.10.0 was awaiting Chocolatey review while version 0.9.1 remained available there. source
- Platforms
- RMUX documents native support for Windows, macOS, and Linux; Windows uses ConPTY and named pipes, while macOS and Linux use Unix PTYs and Unix-domain sockets. source
- Purpose
- RMUX is a local terminal multiplexer written in Rust, with daemon-owned shells and SDK automation. source
- Purpose
- RMUX is a local terminal multiplexer for persistent, scriptable terminal sessions and terminal automation. source
- SDKs
- Official SDKs are available for Rust, Python, and TypeScript. source
- Security
- During Web Share, shells and PTYs stay on the local daemon while the browser decrypts encrypted terminal updates locally; tunnels carry encrypted frames. source
- Security boundary
- The maker says tunnels see handshake metadata and encrypted frames but cannot read keystrokes, PINs, raw tokens, or terminal cells. source
- Self-hosting
- The Web Share frontend is open source and can be built and served from a user's own domain. source
- Sharing roles
- Web Share supports read-write operator and read-only spectator links, with separate pairing PINs by default. source
- Terminal automation
- Its SDKs can send keys, wait for output, take structured snapshots, and subscribe to pane events. source
- tmux compatibility
- RMUX 0.10.0 offers a tmux-compatible 90-command surface with persistent sessions and detach/reattach. source
- Tunnels
- Built-in sharing options include private Tailscale access, public SSH tunnel presets, and user-provided ingress URLs. source
- Web Share
- Web Share creates browser links for a pane or session while the shell stays on the user's machine and the browser decrypts encrypted frames locally. source
- Web sharing
- Web Share provides operator and read-only spectator browser links for a pane or session, with PIN pairing enabled by default. source
Checked against the maker's pages on 9 Oct 2026.