1 Session code & invite
The engineer types the same passphrase on the join page. It is never uploaded and never put in a link — both sides derive the key locally with PBKDF2 (case-insensitive; dashes and spaces are optional).
What's the difference between the three?
Off: serial data is plaintext on the relay (yellow banner above).
Link key: a random 256-bit key rides in the invite link's # fragment — strongest, but a long link.
Passphrase: both sides type the same passphrase, no long link to share; shorter passphrases are easier to
brute-force, so use the generated 12 characters.
2 Cloud link
Once the cloud link is up, plug in the console cable below and the remote engineer can reach the device through the invite link.
3 Attach the console port (Web Serial)
The port is normally driven by the remote engineer (parameters, open/close — once “Let remote engineers control the serial port” is on). The buttons below are for first-time attach only: a browser grants a port only on a local tap, so the very first “Open serial” must be done here. After that, the remote side can open and close it freely.
Requires Android + Chrome or desktop Chrome. On a phone, connect a USB-to-RS232 adapter (FTDI / CH340 / CP210x, no drivers) with an OTG cable, then a rolled console cable into the device's Console port. Cisco IOS defaults to 9600-8-N-1. A system permission dialog appears the first time.
4 Message the engineer (photo / clip / text)
Requires the cloud link to be up. Engineers in the session receive it instantly. Photos & clips are uploaded per session only — cleared automatically when it ends.