RMUX
6.7#2 in terminal multiplexersFree planFree planWebAPILinuxmacOS
VisitRMUX vs Shpool
What both publish
| Fact | RMUX | Shpool |
|---|---|---|
| Installation | Install options include package managers, prebuilt installers, and Cargo; the docs say quick installers verify SHA256. | The README documents installation through crates.io with Cargo and through Homebrew on macOS. |
| Integrations | The project documents a ratatui integration widget and a Claude Code teammate mode that runs Claude inside a local RMUX workspace. | The README documents SSH configuration and shell-function patterns for automatically attaching to sessions. |
| License | RMUX is dual-licensed under MIT or Apache License 2.0. | The GitHub repository identifies the project as licensed under Apache-2.0. |
| 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. | Shpool runs on Linux and macOS; Linux is the primary supported platform, and some macOS tests do not pass. |
| Purpose | RMUX is a local terminal multiplexer for persistent, scriptable terminal sessions and terminal automation. | Shpool creates named persistent shell sessions that survive dropped connections. |
| Security | During Web Share, shells and PTYs stay on the local daemon while the browser decrypts encrypted terminal updates locally; tunnels carry encrypted frames. | The repository's Security and quality page reports zero advisories. |
RMUX plans
- RMUXFree
Shpool plans
- ShpoolFree
Pick RMUX if…
RMUX suits developers who want persistent local terminal sessions or programmatic control through an SDK. Its browser sharing and access roles may also suit people who need to share a pane or session with others.
Pick Shpool if…
Shpool suits people who want persistent shell sessions without terminal multiplexing features. It is intended for Linux, macOS, SSH, and command-line workflows.