Codex Mobile cannot reconnect or reset remote connections after access revoked from Mac
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.513.31313 (2867)
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Initially, I successfully connected Codex Mobile to my Mac through the ChatGPT app on my iPhone. Later, for security reasons, I temporarily revoked the mobile connection from the Mac app.
However, after the connection was removed on the Mac side, the same connection and session history still remained on the Codex page in the iPhone app, with the connection indicator turning red. After that, I could no longer find any option to remove the invalid connection from the mobile app.
In addition, the revoked connection now seems to prevent me from establishing a new connection to the same Mac again.
My question is: how can I remove these invalid/revoked connections from the mobile app and create a new connection successfully?
I have reproduced the same issue on three different Macs, so I believe this is unrelated to the specific system or network environment.
What steps can reproduce the bug?
- Set up a Codex Mobile connection between the iPhone and the Mac.
- On the Mac, revoke the iPhone’s access via:
Settings → Connections → Control this Mac → Devices that can control this Mac
- The iPhone is successfully removed from the Mac-side Codex app. However, the Mac connection and session history still remain in the mobile Codex app, with the connection indicator turning red.
- There is no way to remove or forget the revoked connection from the phone side. The only available option is a toggle for turning the connection on or off, but it does not resolve the issue.
- Attempt to re-establish the connection by scanning the QR code again. The reconnection fails.
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This sounds like a stale enrollment split across at least three places: the Mac-side allowlist, the backend/device enrollment record, and the mobile-side cached connection row. Revoking on the Mac clearly updates one layer, but the phone still appears to hold a stale connection that can block fresh pairing.
A useful recovery contract would separate:
disconnect live access— stop the phone from controlling the Mac now.remove stale mobile row— let the phone forget the old Mac/environment id.regenerate host identity / pairing token— let the Mac publish a fresh enrollment path.Without all three, users can end up in the state you describe: revoked enough to be unusable, but not forgotten enough to pair again. If you have any failed pairing request id from the mobile side after rescanning the QR code, that would probably help maintainers tell whether the backend is rejecting the old mobile client id or the Mac is not publishing a new host identity.