Stream a live shell over WebRTC with a clean Google OAuth handshake. Bypass SSH relays for secure, peer-to-peer remote execution — your terminal bytes never touch our servers.
$npx share-terminal startDevelopers don't switch tools unless the technical superiority is obvious. Here's the landscape — and the exact gap share terminal fills.
Most "share your terminal" tools relay every keystroke through their backend. We don't. Here's the exact lifecycle.
Host and viewer authenticate via Google OAuth. The server matches the two sub claims before issuing any pairing token.
The server passes offer / answer / ICE candidates between the two browsers over a 10-minute JWT-authenticated WebSocket. It never reads frame payloads.
Once ICE completes, a direct DTLS-encrypted SCTP DataChannel forms between host and viewer. The server is out of the path.
We don't ask you to trust us. We ask you to read the protocol — it's short and we link straight to it.
Terminal bytes flow directly between host and viewer over a WebRTC DataChannel. The server only brokers the initial handshake — it never sees a single keystroke or character of output.
The DataChannel runs over DTLS-secured SCTP. Anyone sitting between the two browsers — ISP, proxy, observer — sees only ciphertext.
No session recordings. No transcripts. No log of commands. Redis holds the pairing code for 2 minutes — that is the entire footprint.
The viewer must sign in with the same Google account as the host. Leaked codes are useless — claim attempts are rejected with 403.
Session JWT to the signaler expires in 10 minutes and is bound to a single session, sub, and role. Replays don’t cross sessions.
A 7-byte framing protocol on top of one DataChannel. The whole CLI is 140 KB and you can read the entire wire layer in an afternoon.
Browsable shells unlock workflows that ssh-tunneling tools can't safely do. Two pillars where the architecture pays off, and a handful of adjacent wins.
Leave share-terminal running on your laptop in private mode. Open the join page on your phone's browser, claim the code with the same Google account, and you're typing into your laptop's shell — Claude Code, Codex, vim, anything. Build apps on the train.
See the full use caseShare a live PTY with a teammate. They watch your output and can type into the same shell — every keystroke flows directly between your machines over WebRTC. No video stream, no input lag, no "wait, can you scroll back up?"
See the full use caseYour customer runs one outbound command. You join from a browser and drive their shell. No inbound firewall changes, no SSH keys, no VPN provisioning — and terminal bytes never cross our servers or yours.
See the full use caseCandidate runs the CLI on their own machine. Interviewer joins from a browser and can take over to demo or unblock. You see exactly who claimed the code before any bytes flow.
Leave a repro, a deploy, or a flaky-test loop running. The next engineer picks up the same live PTY in their browser and continues from your cursor — no rebuild, no "what state were you in?"
Real TUIs — vim, k9s, lazygit, your own product — running on a host you control, driven by a prospect with zero install. Closer to a demo console than a recorded GIF.
A student hits a wall on their own machine. They start a private session; you join, type the fix in their actual environment, leave. No "share your screen" gymnastics.
$ npx share-terminal startThe CLI signs you in with Google (device flow), asks the server for a 6-digit pairing code, and waits.
enter code · 482017The viewer opens the web app, signs in with the same Google account, and types the code. The server matches the two identities and hands both sides a short-lived session token.
→ datachannel openBoth ends exchange offer/answer/ICE through the signaling server. The moment ICE completes, an encrypted DataChannel forms between them — the server steps out.
$ vim ~/.config/st/...PTY output streams as OUTPUT frames, keystrokes return as INPUT, resize as RESIZE. Bytes never touch a relay. Close the tab and the CLI exits.
No global install. No SaaS dashboard. No account to provision — sign in with Google, pair, share.
$npx share-terminal start