Codex mobile : Stale codex mobile connections #22902

Activity

1. green-0-rabbit

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on May 15, 2026
2. green-0-rabbit

   changed the title [-]Stale codex mobile connections[/-] [+]Codex mobile : Stale codex mobile connections[/+] on May 15, 2026
3. etraut-openai

   added

   bugSomething isn't workingSomething isn't working

   remote

   on May 15, 2026
4. dingjianhui123-create commented on May 31, 2026

   

   dingjianhui123-create

   on May 31, 2026 – with ChatGPT Codex Connector

   More actions

   Adding a Windows/Codex Desktop + ChatGPT iOS data point for stale mobile connection records.

   Environment observed:

   Desktop OS: Windows
   Codex Desktop package: OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
   Mobile client: ChatGPT iOS Codex remote access
   

   Observed behavior:

   • The iOS Codex view shows the current desktop host online with a green dot.
   • The same view also shows an older LAN/IP-style host entry offline with a red dot.
   • The old offline entry appears to be from a previous local network/IP state and remains visible after the current desktop host is online under its normal host name.

   Local evidence from the Windows desktop side:

   • Current desktop hostname is online and enrolled.
   • Current LAN IP differs from the stale red/offline IP shown on mobile.
   • Local remote_control_enrollments only shows one current Codex Desktop enrollment for the live host.
   • Local state has codex-mobile-has-connected-device = true and remote-project-connection-backfill-completed = true.
   • Logs show codex_chatgpt_ios_remote successfully resuming a desktop thread, so mobile remote access itself is not completely broken.

   Expected behavior:

   • Mobile should either hide expired/offline stale host records once the live host is available, or expose a clear remove/disconnect action for those stale records.
   • Stale LAN/IP-derived entries should not make users think they are connected to the wrong machine.
   • If the stale entry is server-side state, there should be a supported reset/purge path from Codex Desktop or mobile.