CODETETHER GUIDE

Account and devices

Account, control-device authorization, and execution-machine trust answer different security questions.

Account ownership

An account identifies the person and product devices that belong together. The public website does not currently have a connected production authentication service, so it cannot display or change live account information yet.

Control-device authorization

A phone or tablet needs explicit product-device authorization. Revoking that authorization should remove the device’s account-level access without inventing a replacement machine identity.

Machine pairing trust

Machine trust is a pinned Controller-to-Node relationship created by the supported pairing flow. Account login does not create, replace, or silently revoke this trust.

Device capacity

Free to download. Includes 1 execution machine and 1 control device — a phone or tablet. A phone and tablet share the same control-device slot. The product has not announced pricing or enforcement rules beyond this base allowance.

Revocation

  • Use the existing product flow for the exact authorization or trust relationship you intend to revoke.
  • Removing a project location does not delete files on the remote machine.
  • Unpairing remains separate from account sign-out and may require project locations to be removed first.
  • Do not delete private state or regenerate identities as a shortcut for ordinary revocation.

CodeTether never treats a lost network response as permission to replay provider work automatically. When execution ownership is uncertain, inspect the conversation before starting a fresh task.