End-to-end encrypted
Protocol v2 encrypts terminal data and durable device credentials between the browser and agent. The relay cannot read terminal plaintext.
42 O’Clock TermHop · public beta
Your terminal, without giving the relay the transcript.
TermHop connects a phone or desktop browser to a Linux, macOS, or Windows computer. Terminal data is encrypted between the browser and agent; the relay routes ciphertext and connection metadata.
Authenticated pairing
Scan a terminal QR code or paste a short-lived pairing link. The browser pins the agent public key before a session starts.
Runs where you work
Per-user agents support Linux, macOS, and Windows 10/11. The browser client works on a current phone or desktop browser.
Try it without installing anything
The disposable demo starts an isolated Linux environment and connects it automatically. It runs for at most 10 minutes, exposes an exact activity allowlist rather than a general shell, and is destroyed at logout or expiry.
Connect your own computer
Install the Python 3.11+ agent as your normal OS user, pair it to a reachable wss:// relay, and open the public browser client. Persistent user services are available for systemd, launchd, and Windows Startup.
Self-host the relay
Docker Compose is the recommended production path. Put the relay behind an HTTPS/WSS reverse proxy, keep its local port and Redis private, and restrict browser origins. A hardened native Linux/systemd deployment is also documented.
A separate boundary from Control
Control observes infrastructure and exposes narrowly governed operations. TermHop owns interactive terminal access. Keeping them separate makes the privilege and failure boundaries easier to inspect.
Next step
Run TermHop your way.
Read the install guide, deploy a relay, or inspect the public AGPL source before pairing a machine.