Unpairing a machine

If a machine is ever compromised, lost, or simply no longer something you want controllable this way, unpairing happens from the tAI web app's own Remote Control settings, not from the terminal on the machine itself.

This is deliberate: if the machine is genuinely lost or compromised, you may not have terminal access to it anymore to run an unpair command locally, so the control surface lives somewhere you can always reach.

tCode notices the pairing has been revoked on its very next attempt to reconnect and clears its own local state automatically at that point, with nothing further required on the machine's end.

Unpairing does not affect anything about local use of tCode on that machine; it only removes the remote-control path in. Signing in and working directly in the terminal continues exactly as before, on that machine or any other.

If a machine is unpaired by mistake, re-pairing it is exactly as simple as the original setup, a fresh code from a new Remote Control chat and one /pair command; there is no waiting period or additional verification required to pair it again.