muxterm vs WMUX

Muxterm is a free, self-hosted terminal multiplexer with a browser interface and a Go session daemon. Users can split panes, group them into named workspaces and switch workspaces from a bar. The daemon runs separately from the HTTP server, allowing shells to persist across server restarts, deployments and reboots. Server-side VT emulation retains a live screen snapshot that can restore full-screen applications after reconnecting. Its installable PWA supports desktop and mobile use, with service-worker offline support. For MCP-compatible agents, the server provides 25 tools across seven categories for managing workspaces, panes, terminals and other functions. Documented integrations include Claude Code, OpenCode and Amplifier; lifecycle reporting is available for Claude, Codex and Amplifier wrappers. Authentication uses HMAC tokens, with a localhost bypass for local use. A file-publishing tool can expose one local file at an unguessable public URL, with a 24-hour default expiry, a seven-day maximum and revocation for future reads. The project is MIT licensed and self-hosted as a single binary. Windows support is listed as coming soon.

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 scope is intended for shells, servers, logs, builds, agents, and project work. Users can split panes left or right, or top or bottom, navigate among them, and zoom a pane. WMUX creates a default configuration file on first use, with commands to inspect its path, contents, and effective configuration. It runs on Linux, macOS, and Windows; Windows uses native platform mechanisms without a POSIX emulation layer. The software is free and MIT-licensed. Windows ARM64 builds and package-manager repositories are not currently provided. Release archives have SHA-256 sidecar files, and GitHub attestations can be used to verify build provenance. Its v1 binaries are not Authenticode-signed or Apple-notarized, so Windows SmartScreen or macOS Gatekeeper may show a trust prompt.