Support multi-account and multi-machine Codex mobile Remote Control connections

Summary

Please support first-class multi-account and multi-machine connections for Codex mobile Remote Control.

Right now, Codex mobile Remote Control appears to work best when there is a single active desktop host / enrollment. In real development setups, users often have multiple ChatGPT accounts or workspaces and multiple machines, and the current model can become confusing or fragile.

Problem

Common real-world setups include:

• A personal ChatGPT account plus a Business / Enterprise workspace.
• Multiple desktop hosts, for example a Windows workstation, a Mac laptop, and an SSH / devbox environment.
• Multiple Codex Desktop sessions or app-server owners over time.
• Switching between accounts on the same desktop install.

In these cases, Codex mobile Remote Control can become hard to reason about:

• Mobile may show only one available host instead of multiple authorized machines.
• A newer host can appear to overwrite or hide a previous host.
• A stale host can remain visible as offline.
• Switching accounts can leave stale enrollment state behind.
• Desktop can fail enabling Remote Control with messages such as:

Could not enable remote control. Please ensure only one instance of Codex is running.

This makes it unclear which account, workspace, machine, and project the mobile app is actually connecting to.

Expected behavior

It would be useful if Codex mobile Remote Control supported a clearer multi-host / multi-account model:

• Mobile lists multiple authorized Codex desktop hosts per account / workspace.
• Each host has a stable identity, display name, platform, workspace/account scope, and last-seen status.
• Desktop host enrollment is scoped by account, workspace, and machine, instead of being overwritten by another host.
• Users can revoke, forget, or reset stale hosts from both desktop and mobile.
• Switching accounts on the same desktop install cleanly switches or re-enrolls the host without leaking stale state from the previous account.
• The UI clearly shows which host, account/workspace, project, and execution environment will receive the remote session.
• If only one active instance is allowed, the app should identify which instance is blocking enrollment and offer a safe cleanup path.

Why this matters

Codex is often used across several development contexts, not just one laptop:

• Personal projects vs. company workspace.
• Windows desktop plus Mac laptop.
• Local projects plus SSH / remote Linux projects.
• Long-running tasks that users want to monitor or continue from mobile.

For these users, mobile Remote Control becomes much more useful if it can explicitly manage multiple machines and multiple account/workspace enrollments.

Related issues

This request is related to several existing reports around host identity, stale enrollments, account switching, and mobile Remote Control behavior:

• #22950
• #23339
• #23977
• #23082

Those issues each cover important individual cases. This issue is a broader product request for a clear, supported multi-account / multi-machine connection model.

Environment

Observed while using Codex Desktop on Windows with the mobile Remote Control flow. The exact machine/account identifiers are intentionally omitted.