amux vs muxterm

amux is a terminal multiplexer for shared workflows in which people use keybindings and agents use CLI commands in the same panes. Users can create and arrange panes, manage windows, zoom panes, and broadcast keystrokes to multiple panes. Its CLI offers structured JSON session capture, blocking waits, and push-based events without requiring an SDK or language-specific library. Pane history stays on the server and can survive detach and reattach, server reload, and crash recovery; the default scrollback is 5,000 lines per pane. A built-in mailbox lets panes send, read, reply to, and acknowledge messages, with recipients checking an inbox instead of receiving automatic PTY input. An optional local MCP server over stdio exposes mailbox tools. Remote panes and windows can be mirrored over SSH, forwarding input and streaming remote PTY output. The repository documents Claude Code and Codex integrations, including mailbox-drain hook recipes. amux is MIT licensed and free, with installation through a shell script, Homebrew, or go install. The first server start installs a terminfo entry and requires ncurses tic. It runs on Linux and macOS, but does not implement every tmux feature, including session groups and advanced hooks.

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.