Pairing a machine

A machine running tCode can be paired once with the tAI web app, then triggered from a browser tab on any device afterward, without opening that machine's terminal again.

Pairing a machine

Once paired, this connection is remembered: the next time tcode starts on this machine, it reconnects to the same remote chat automatically, no code needed again.

One worker, one queue

A prompt sent from the browser is added to the same queue a locally typed message would go through, processed by the same single worker that runs every turn on that machine.

How permission prompts work remotely

Permission prompts work differently for a remote-triggered turn than for a local one.

Unpairing a machine

If a machine is ever compromised, lost, or simply no longer something you want controllable this way, unpairing is done from the tAI web app's own Remote Control settings, not from the terminal; tCode notices the pairing has been revoked on its next attempt to reconnect and clears its local state automatically.

Why pairing codes are single-use

A pairing code is single-use and short-lived, generated fresh each time you open a Remote Control chat in the web app specifically to pair a new machine.

Output relayed to the browser live

Output from a remote-triggered turn is relayed to the browser as it happens, the same tool headers, the same permission prompts, the same closing summary described in Outputs, rather than only appearing once the whole turn finishes.

Watching a remote turn from the local terminal too

If you are sitting at the paired machine's own terminal while a remote-triggered prompt is sent, you will see it appear there too: local output and remote output share the same terminal window, since it is genuinely the same tCode process handling both, just relaying a copy of everything to the browser as well.

Per machine, not per account

Pairing only ever grants control of the specific machine it was set up on.