amux vs TermStation

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.

TermStation is a web-based terminal session manager with an API for organizing sessions across multiple machines. Configurable templates set CLI commands and arguments, then shape the forms used to create sessions. Session and workspace scratch pads, session links, and file generation with macros and includes support day-to-day work. It can launch commands in containers and route HTTP access to web servers in those containers through a reverse tunnel. Multiple users can work with role-based access and share sessions. Configurable code-forge integrations include GitHub by default; the maker also demonstrates installing Claude, Codex, and Cursor in a container. TermStation is open source under the MIT license and free. It is marked pre-alpha and not ready for general distribution. Backend requirements include Ubuntu 22.04+ or Rocky Linux 10+, Node.js 22+, and Docker or Podman. Authentication exists, but the maker says it is not hardened for untrusted networks and advises against public exposure. Session data must be deleted manually until automatic cleanup is implemented.