Devices and pairing
Connect to multiple computers and manage local trust.
Device IDs and names
The connection service allocates six-digit device IDs. IDs belong to that service. If you change services, pair again using the ID issued by the new service.
The device list retains names and connection information. Desktops use the system device name; browsers derive a name from browser information. Adjust the local name in settings to distinguish computers.
Multiple computers
A controller can remember multiple hosts. Choose a device, then one of its projects and sessions. Mobile navigation moves from devices to sessions to full-screen chat; Back returns one level at a time.
On desktop, the default view is the local agent dashboard. Selecting a remote device opens that computer's sessions.
Trust and revocation
First pairing needs confirmation on the host or verification of a configured password. Pairing keys stay local to the controller. Signing in synchronizes a device directory, not private pairing keys to a new browser.
After using a public computer, clear controller data and revoke its authorization on the host. Clearing browser data alone does not revoke host-side trust.
Official account sync
Native clients use a browser authorization code to sign in and bind the device. After confirmation on the account page, the same account can synchronize its directory; new controllers still need pairing.
Official quotas count host computers. Phones and browser controllers do not occupy host slots. Codex App and CLI count as one Codex product. See Account and plans for current entitlements.