muxterm vs TermStation

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.

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.