TermPair

Screenshot

About TermPair

TermPair lets you share and control a remote terminal from any browser with end-to-end encryption. Running `termpair share` prints a link that grants live access to your terminal session output is encrypted with AES-128-GCM before leaving the terminal, and the server acts purely as a blind relay that never sees plaintext data or encryption keys. Viewers can type into the shared terminal by default, or the session can be set to read-only to keep them watching without control. Sessions can be kept private (encrypted, link-only) or made public and listed on the landing page for anyone to discover. If the server restarts, both sides automatically reconnect and resume where they left off. TermPair ships as a single static binary bundling the server, client, and web frontend, requiring no Node, Python, or Docker, and runs on Linux, macOS, and Windows, sharing any terminal application with a TTY a shell, vim, htop, or tools like Claude Code. Three rotating AES-128-GCM keys secure each session, with the bootstrap key delivered via a URL hash fragment that's never sent to the server. Browsers render output using xterm.js and the Web Crypto API, and require a secure context (HTTPS or localhost). TermPair is open source and released under the MIT License.

Key Features

• Share a live remote terminal via a single browser link
• End-to-end AES-128-GCM encryption; server is a blind relay
• Viewers can type in the terminal, or be restricted to read-only
• Private (link-only) or public (discoverable) session modes
• Automatic reconnection and session resume after server restarts
• Single static binary, no Node/Python/Docker dependencies
• Cross-platform: Linux, macOS, and Windows
• Share any TTY-based app: shell, vim, htop, and more
• Key rotation every 2^20 messages with monotonic IV counters
• Browser rendering via xterm.js and the Web Crypto API
• NGINX and systemd deployment examples included
• Self-signed TLS certificate support for self-hosting

Useful Links