Reference build · Remote Desktop spec v2

Remote Desktop

A serverless WebRTC screen-share, file-transfer and remote-view tool that runs entirely in two browsers — no accounts, no relay server, no session data leaving the two machines. It's the working embodiment of the spec's security model: the session code locates, a verbal code authenticates, and the host approves each capability before anything is shared.

Read the full spec (v2) ↗
How the connection works. This build has no rendezvous server, so you exchange one connection code by hand (message / email / phone). Real products replace this hand-off with a short-ID server — see the spec's §4 and Track B. Everything after the hand-off is peer-to-peer and encrypted by WebRTC's DTLS-SRTP.

01Approve capabilities

Consent is capability-scoped, not one switch. You grant exactly what the controller may do. Nothing is shared until you press Start hosting.

02Send your connection code

Send this code to your controller by any channel you trust. It locates your machine and carries your encryption fingerprint — it is not a password.

— — —Session locator · shareable, not secret

03Paste the controller's reply

Your controller pastes their reply code back to you. Paste it here to finish the connection.

04Confirm you're talking to the right person

WebRTC encrypts the link but does not prove who is on the other end. Read this code aloud. If it doesn't match on both screens, someone is in the middle — hang up.

······ Compare verbally with the controller. This is a Short Authentication String derived from both encryption keys (spec §5.1).

05Live session

Connected Path: … Controller sees: your screen
Your shared screen preview

Chat

Files

Chunked, hashed, verified end-to-end. Received files download to disk and are never executed (spec §5.7 / B8).

Drop a file or click to send

01Paste the host's connection code

Your host (the person you're helping) sends you their code. Paste it here to locate their machine.

02Send your reply code back

Send this reply to your host by the same channel. Once they paste it, you'll connect.

03Confirm the security code

Read this aloud with your host. Matching codes prove the encrypted link is direct, with no one in the middle.

······ Short Authentication String — must match the host's screen exactly (spec §5.1).

04Host screen

Connected Path: …
Waiting for the host's screen…

Chat

Files

Received files download to disk and are never executed.

Drop a file or click to send