You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mac-to-Mac remote control fails in both directions, while iPhone works #27231
What version of the Codex App are you using (From “About Codex” dialog)?
26.602.71036
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Mac-to-Mac remote control in the Codex macOS app fails in both directions.
Two Macs are signed into the same account/workspace. Both devices appear online in Settings > Connections > Control other devices. Adding and removing the connection works, but connecting fails with:
"Verbindung konnte nicht aktualisiert werden"
"Verbindung fehlgeschlagen"
This happens in both directions:
Mac A -> Mac B fails
Mac B -> Mac A fails
Important detail:
Remote control from the ChatGPT iPhone app to both Macs works immediately. That suggests the account/workspace, relay, and host-side remote access are functioning, and the issue seems specific to Mac-to-Mac remote control in the Codex macOS app.
I hit a related remote-control pairing issue, but in my case the root cause was likely Migration Assistant.
Setup:
I migrated data from an old MacBook Pro to a new MacBook Air using macOS Migration Assistant.
Both machines were signed into the same Codex account/workspace.
The Pro already had Codex remote control enabled.
Symptom:
I could not enable mobile remote control for the new MacBook Air while the Pro remote control was enabled.
It looked like Codex was treating the Air and Pro as the same remote host/device.
Refreshing/re-pairing would make one device affect the other.
Debugging:
The Air’s macOS hostname was correct and distinct.
But Codex local state on the Air still contained remote-control identity data inherited from the Pro.
In particular, clearing only the remote_control_enrollments row was not enough.
The important migrated value was ~/.codex/installation_id; Codex appeared to derive/reuse the remote host identity from that.
What fixed it:
Quit Codex completely on the new Mac.
Back up:
~/.codex/.codex-global-state.json
~/.codex/installation_id
~/.codex/state_5.sqlite*
Remove Codex remote-control keys from .codex-global-state.json.
Delete rows from the SQLite table remote_control_enrollments.
Replace ~/.codex/installation_id with a fresh UUID.
Reopen Codex and pair remote control again.
After rotating ~/.codex/installation_id, the new MacBook Air got a fresh remote identity and remote control pairing worked.
So for users who set up a second Mac via Migration Assistant, this may be a duplicated local Codex installation identity issue rather than a network/account/workspace issue.
Activity
github-actions commentedon Jun 9, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
BochaoKong commentedon Jul 5, 2026
I hit a related remote-control pairing issue, but in my case the root cause was likely Migration Assistant.
Setup:
Symptom:
Debugging:
remote_control_enrollmentsrow was not enough.~/.codex/installation_id; Codex appeared to derive/reuse the remote host identity from that.What fixed it:
~/.codex/.codex-global-state.json~/.codex/installation_id~/.codex/state_5.sqlite*.codex-global-state.json.remote_control_enrollments.~/.codex/installation_idwith a fresh UUID.After rotating
~/.codex/installation_id, the new MacBook Air got a fresh remote identity and remote control pairing worked.So for users who set up a second Mac via Migration Assistant, this may be a duplicated local Codex installation identity issue rather than a network/account/workspace issue.
sohantanna commentedon Jul 10, 2026
@BochaoKong worked perfectly! Thank you so much!