‹ Guides

Reaching your AI machine: who can see what

When Term connects to the computer that runs your coding agents, only your phone and that computer can read the session — not us, not the relay in between. Here is how the keys, the pairing code and every connection work, and exactly what our service does and does not see.

In progress · Written

When you reach the computer that runs your coding agents from Term, your terminal travels over networks you do not control, and sometimes through a relay we run. So the first question is fair: can anyone in between see what you type, or what your agents print?

No. Only your phone and your computer hold the keys that open a session. Our service helps them find each other and can pass sealed packets along, but it cannot read them, and it cannot add a device to a computer you have already paired. This post shows how, with no prior knowledge needed. There is a short technical section at the end for the curious.

Who holds which key

Your phone on the left and your computer on the right, each with an amber key labelled private key: on the phone, kept in the phone's secure storage; on the computer, never leaves this computer. Under the computer, a green box: Trusted devices — your phone ✓ — only the computer writes this list. In the middle, a dimmed cloud labelled Our service: holds no keys, cannot add a device, with a crossed-out key.
One key each, two devices, no copies. The service in the middle has none, and the list that decides who may connect lives on your computer.

Pairing, once

Your computer shows a one-time code, K7Q2-9XMF-4TRW, labelled single use, expires in 5 minutes; a dashed amber line takes it to your phone. Two boxes below: a green secret that stays on your phone and your computer, and a blue lookup handle — the only part our service sees — with a dashed line to the cloud labelled Our service: can find your computer, is never told the code.
One code, two parts. The secret part never leaves your two devices; our service only ever sees a lookup handle made from it.

The helper on your computer shows a twelve-character code (and a QR code of the same thing). You type or scan it on your phone once.

Every connection

Your phone on the left and your computer on the right. A solid green line between them, labelled direct, carries sealed envelopes with padlocks: sealed with keys only these two have. Above, a blue dashed path through a cloud labelled Relay — through a relay, only if needed — also carries sealed envelopes; the relay sees sealed packets and a connection number. At the bottom, a pill: Our service answers “where is it?”
Direct when the network allows, through a relay when it does not — sealed either way.
  1. Your phone asks our service where your computer is (its current addresses, and a relay to use if needed).
  2. Your phone and your computer prove who they are to each other. Each shows it holds its private key, and your computer checks the phone against its own trusted list. A device that is not on the list gets nowhere.
  3. That exchange produces fresh keys for this session only. Every packet after it — what you type, what your agents print — is sealed with them.
  4. The packets go straight from phone to computer whenever the network allows. When it does not (some home routers and mobile networks block it), they go through a relay. The relay forwards sealed packets and nothing else: it holds no key that could open them, and none that could make it look like your phone to your computer. What it does see is both ends' network addresses, a connection number, and the timing and size of the packets.

A forged or tampered packet is rejected, and a replayed one changes nothing.

What our service sees, and what it does not

Our service can seeIt never sees
The devices and computers on your account: their public keys, names (your phone's model; a computer's name defaults to its hostname), OS and version, app or helper version, first and last seenWhat you type
Network addresses: a computer's public address and its local ones, and your phone's public address when it connectsWhat your agents or programs print
Which computer each phone looks up, and when; whether it was last reached directly or through a relayCommands, file names, folders, window titles, session names
For each computer, every ~25 s: how many sessions are open, how many are waiting for you, and its loadYour pairing codes, or any key

Your account appears there only as an anonymous ID; the link to your Huawei account is held by our separate account server. The relay additionally sees the addresses, timing and amount of data for connections it carries. And any device that knows a computer's public key — including a phone you have removed — can ask where that computer is and whether it is online; it still cannot connect.

What happens if…

What this does not protect

The keys keep everything between your devices private. They cannot help if your phone or your computer itself is compromised: whoever controls the computer controls its shells anyway. Keep both up to date, use a screen lock on your phone, and remove devices you no longer use.

For the technically curious