WMUX
WMUX is a terminal multiplexer that keeps local terminal workspaces alive when a terminal client disconnects.
What WMUX is
WMUX is a terminal multiplexer that keeps local terminal workspaces alive when a terminal client disconnects. Its persistent server manages sessions, windows, panes, terminal state, layouts, options, commands, paste buffers, jobs, and clients. That can keep shells, servers, logs, builds, agents, and project workspaces active across a disconnection.
Users can split panes left or right, or top or bottom, move between panes, and zoom a pane. WMUX creates a default configuration file on first use and provides commands to inspect its path, contents, and effective configuration. It runs on Linux, macOS, and Windows; on Windows it uses native platform mechanisms without a POSIX emulation layer. WMUX is available under the MIT License, with no pricing or usage limits stated. Windows ARM64 builds and package-manager repositories are not currently provided. Release archives include SHA-256 sidecar files, and GitHub attestations can verify build provenance. The v1 binaries are not Authenticode-signed or Apple-notarized, so Windows SmartScreen or macOS Gatekeeper may show a trust prompt.
Good
- Keeps terminal workspaces active after disconnection.
- Supports splits, pane navigation, and zoom.
- Creates a default configuration file on first use.
- Runs on Linux, macOS, and Windows.
- Available under the MIT License.
Watch out
- Windows ARM64 builds are not provided.
- Package-manager repositories are not provided.
- v1 binaries are not Authenticode-signed or Apple-notarized.
- Trust prompts may appear on Windows or macOS.
Who it suits
WMUX suits people who need local terminal workspaces to persist across client disconnections, including for shells, servers, logs, builds, agents, or projects. It is available on Linux, macOS, and Windows.
Verdict
WMUX provides persistent local terminal sessions across three desktop platforms, with pane controls and configuration inspection commands. Windows ARM64 availability and binary trust prompts are worth considering before installation.
Plans and prices
From WMUX's own pricing page, checked 5 Oct 2001.
| Plan | Price | What it gives you |
|---|---|---|
| wmux | Free | MIT-licensed; no pricing or usage limits stated |
The facts
Each one read from WMUX's own pages, with the date it was checked.
What it does
- Configuration
- WMUX creates a default configuration file on first use and provides commands to inspect its path, contents, and effective configuration.checked 5 Oct 2001
- Distribution limits
- Windows ARM64 builds and package-manager repositories are not currently provided.checked 5 Oct 2001
- Integrity
- Release archives include SHA-256 sidecar files, and users can verify build provenance with GitHub attestations.checked 5 Oct 2001
- Intended users
- The project describes WMUX for people who need persistent terminal workspaces for shells, servers, logs, builds, agents, and projects.checked 5 Oct 2001
- License
- WMUX is available under the MIT License.checked 5 Oct 2001
- Panes
- Users can split panes left/right or top/bottom, navigate between panes, and toggle pane zoom.checked 5 Oct 2001
- Purpose
- WMUX is a persistent terminal multiplexer that keeps shells, servers, logs, builds, agents, and project workspaces alive when a terminal client disconnects.checked 5 Oct 2001
- Security reporting
- The project asks users to report vulnerabilities through the private process in its security policy rather than through a public issue.checked 5 Oct 2001
- Sessions
- Its persistent server manages sessions, windows, panes, terminal state, layouts, options, commands, paste buffers, jobs, and clients.checked 5 Oct 2001
- Signing
- The v1 binaries are not Authenticode-signed or Apple-notarized, so Windows SmartScreen or macOS Gatekeeper may show a trust prompt.checked 5 Oct 2001
Where it runs
- Platforms
- Release targets include Windows x86-64, Linux x86-64 and ARM64, and macOS Intel and Apple Silicon.checked 5 Oct 2001
- Windows support
- WMUX uses native platform mechanisms and does not require a POSIX emulation layer on Windows.checked 5 Oct 2001
