RMUX

RMUX is a Rust terminal multiplexer for persistent local shells, with SDKs that let code control terminal sessions. It is best suited to developers who want automation or optional browser sharing without moving their shells off their own machine. Its open-source, no-cost model is attractive, but remote collaboration requires setup.

Overview

A local daemon owns RMUX shells, so sessions can persist through detaching and reattaching. Version 0.10.0 offers a 90-command tmux-compatible surface, which should make it a practical fit for users who want familiar multiplexer operations alongside programmable control. Persistence is local: RMUX is not a hosted terminal service.

Control defaults to local IPC. Browser sharing and remote access require explicitly starting Web Share, and remote access also needs a tunnel or ingress. That opt-in design limits routine network exposure, but puts setup and access management on the user.

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. This makes RMUX more compelling for scripts and tools that need to coordinate terminal work than for users who only need a basic multiplexer. Python and TypeScript projects require the RMUX binary to be installed first; that extra prerequisite matters when packaging or onboarding those tools.

Browser sharing and security

Web Share creates browser links for a pane or session while the shell and PTY remain on the local daemon. Read-write operator and read-only spectator roles, with separate pairing PINs enabled by default, let an owner grant different levels of access. Browser clients decrypt terminal frames locally; the stated design derives per-connection keys with X25519, ML-KEM-768, and HKDF-SHA256, then encrypts frames with ChaCha20-Poly1305. Tunnels carry handshake metadata and encrypted frames, not readable keystrokes, PINs, raw tokens, or terminal cells according to the maker.

Sharing can use private Tailscale access, public SSH tunnel presets, or a user-provided ingress URL. The Web Share frontend can also be built and served from a user's own domain. These options suit technically capable users who want to manage their own access path; they are less convenient than a hosted service that handles remote connectivity for them.

Other 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, or Cargo, and quick installers verify SHA256. Windows package availability is uneven: version 0.10.0 was awaiting Chocolatey review while 0.9.1 remained available there.

Pricing

RMUX: free. The plan is open source under a dual MIT or Apache-2.0 license and runs as self-hosted local software. There are no paid tiers or seat and usage quotas described for this plan, so it is a strong fit for individuals and teams willing to install and operate the software themselves. Its cost advantage does not remove the work of configuring tunnels or ingress for remote access.

Platforms

RMUX supports Linux, macOS, and Windows, with local CLI access, a browser interface through Web Share, and Rust, Python, and TypeScript SDKs. The Python and TypeScript SDKs depend on the installed binary, so they are not standalone alternatives to the local runtime.

Who it's for

Choose RMUX if you want persistent local sessions, need to automate terminal interaction through code, or want role-based browser sharing while keeping shells on your machine. Self-hosters who value control over network exposure also have several tunnel and ingress choices. Look elsewhere if you need a managed hosted terminal, want remote sharing without configuring connectivity, or cannot install the local runtime required by the SDK workflow.

Pros and cons

• Pro: Persistent sessions and a 90-command tmux-compatible surface combine familiar multiplexer workflows with local daemon ownership.
• Pro: SDKs expose typed handles, input, waits, snapshots, and pane events for code-driven terminal automation.
• Pro: Web Share separates operator and spectator access and keeps shells local while encrypting browser updates.
• Pro: The software is free and dual-licensed under MIT or Apache-2.0.
• Con: Remote access requires deliberately starting sharing and arranging a tunnel or ingress, adding operational setup.
• Con: Python and TypeScript automation requires the RMUX binary, complicating environments where installing a local runtime is impractical.
• Con: Chocolatey users may need to remain on version 0.9.1 while 0.10.0 awaits review.

Alternatives

Browse terminal multiplexers if you want to compare more tools in the category. Consider Okena for a free option spanning mobile as well as desktop platforms. Zellij is another free, open-source choice with no account required; choose it if that account-free setup matters more than RMUX's documented SDK automation and browser-sharing model. muxel is a free, GPL-3.0 option for Linux, macOS, and Windows. muxterm is a free, MIT-licensed self-hosted alternative distributed as a single binary. Herdr is a free Apache 2.0 runtime for local macOS, Linux, and Windows use. LibreBooking is a free, GPL-3.0 resource-scheduling tool, rather than a terminal-multiplexer choice. openmux is a free MIT-licensed option for macOS Apple Silicon and Linux x64 or arm64. p2pmux is a free MIT-licensed alternative for Linux and macOS.

Verdict

RMUX is a strong choice for developers who want programmable, persistent local terminals and can manage their own sharing setup. Its SDKs and encrypted, role-based browser links distinguish its local-first approach, while the binary prerequisite and remote-access configuration are meaningful costs. Choose it for control and automation; look elsewhere for a hosted, ready-to-share terminal.