⬡

PeerTerm

Instant terminal sharing, end-to-end encrypted

Join a session

Enter the 6-digit code shared by the host to connect to their terminal.

End-to-end encrypted

Frequently Asked Questions

Can the relay server see my terminal output or passwords?

No. PeerTerm is designed from the ground up with end-to-end encryption (E2EE). Before any connection starts, the host CLI and viewer perform an ephemeral ECDH P-256 key exchange using the browser's native Web Crypto API.

Every keystroke, terminal output byte, and control packet is encrypted locally using AES-256-GCM with unique 12-byte initialization vectors. The relay server acts strictly as a blind packet forwarder—it only ever sees opaque binary blobs and never possesses the decryption keys.

How do I run PeerTerm behind a corporate firewall?

PeerTerm works behind corporate firewalls automatically without requiring any inbound open ports or router configuration:

  • Direct P2P: It first tries direct WebRTC DataChannel connectivity using STUN for automatic NAT traversal.
  • Encrypted Fallback Relay: If symmetric NAT, strict VPNs, or enterprise firewalls prevent direct P2P connections, PeerTerm automatically falls back to an encrypted WebSocket relay over standard outbound HTTPS/WSS (port 443), which is allowed on virtually all enterprise networks.
  • Self-Hosted: You can also route sessions through your own private relay using the --relay <url> flag.
Does PeerTerm require root or sudo privileges?

No. PeerTerm runs entirely in standard user space. Neither the host command (npx peer-term) nor the web viewer requires administrator or sudo privileges.

The host process simply spawns a pseudo-terminal (PTY) inside your current shell environment, strictly restricted to your current user account's existing file access and system permissions.

How does PeerTerm compare to tmate?

While tmate is an established tmux-based tool, PeerTerm is designed for frictionless web-first collaboration:

  • Zero Viewer Setup: With tmate, peers typically need an SSH client and SSH keys configured. With PeerTerm, viewers just open a web link in any browser on desktop, iPad, or mobile—no software to install.
  • Local P2P WebRTC: When host and client are on the same local network or reachable via WebRTC, PeerTerm establishes a direct peer-to-peer data channel with sub-10ms zero-relay latency.
  • True E2E Encryption: In tmate, relay servers terminate SSH sessions. PeerTerm uses client-side ECDH P-256 + AES-256-GCM encryption, ensuring neither the relay nor any middleman can read or modify session data.
  • Live Permission Toggling: Dynamically toggle active sessions between Read-Only (view-only) and Interactive modes on the fly (r <code>) without restarting or dropping connections.
  • Encrypted File Uploads: Viewers can drag and drop files (up to 100MB) directly into the host's uploads directory.

Have suggestions or feedback? Reach out to me!

Establishing encrypted connection...
PeerTerm
00:00 👁 View Only
⏳ Connecting...
Encrypted
⬡

Session Ended

Thanks for using PeerTerm! If you found it useful, consider giving us a star on GitHub :) it helps a lot!

Way to GitHub