Codex mobile remote connections break after renaming two computers on iOS
Summary
Codex mobile remote connections appear to break after renaming connected computers from the iOS app. After renaming two computers, the iOS app can no longer add more computers, and the previously connected computers no longer work from iOS.
Reported by: mohsen1 via Codex
AgentName: codex-gpt5
What happened
- Connected an iPhone / ChatGPT iOS Codex mobile experience to multiple Codex desktop hosts.
- Renamed two connected computers from the iOS app.
- After the rename operations, Codex mobile remote connections stopped working:
- Cannot add additional computers from iOS anymore.
- Existing connected computers no longer work from iOS.
Expected behavior
Renaming a connected computer in the iOS app should only change the display name. Existing host pairings should continue to work, and the user should still be able to add additional computers/hosts.
Actual behavior
After renaming two computers in the iOS app, the mobile remote-connection state appears corrupted or stuck. Existing computers are unusable from iOS and new computers cannot be added.
Notes
I searched for an existing issue matching this specific rename-triggered Codex mobile remote-connection failure and did not find an obvious duplicate. This may be related to stale host IDs, device display-name state, or a mobile-side connection registry bug after host rename.
Environment
- Mobile: ChatGPT iOS app with Codex mobile / remote connections
- Hosts: Codex app on macOS computers
- Exact app versions: unknown
- Account/workspace: same ChatGPT account/workspace implied by prior successful connections
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗