What version of the Codex App are you using (From “About Codex” dialog)?
26.609.41114
What subscription do you have?
Pro
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
Codex Desktop remote control gets stuck after a controller device is revoked. The remote Mac still appears online and current, but the controlling Mac shows Connection failed and keeps reusing the revoked remote-control client enrollment. There is no visible UI action to reset/regenerate that controller authorization.
What steps can reproduce the bug?
Set up Codex Desktop remote control between two Macs.
From the controlled Mac, revoke access for the controlling Mac.
On the controlling Mac, go to Settings → Connections → Control other devices.
Try reconnecting to the controlled Mac.
Observe that the controlled Mac is visible, online, and on the current version, but the connection fails.
The row’s Delete action is disabled because the remote environment is online.
Toggling the connection, refreshing, restarting Codex, and rebooting do not regenerate the controller enrollment.
What is the expected behavior?
When the backend returns that the remote-control client has been revoked, Codex should clear the local revoked enrollment and create a fresh controller enrollment, or expose a Reset authorization / Reauthorize this device button in the Connections UI.
Additional information
The app log showed:
Remote-control client has been revoked
POST /backend-api/codex/remote/control/client/refresh/start returned 403
The workaround was to fully quit Codex and remove the revoked entry from:
~/.codex/.codex-global-state.json
Specifically under:
electron-remote-control-client-enrollments
After removing the stale client enrollment, Codex created a fresh one on launch and the Mac mini connection worked again.
What version of the Codex App are you using (From “About Codex” dialog)?
26.609.41114
What subscription do you have?
Pro
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
Codex Desktop remote control gets stuck after a controller device is revoked. The remote Mac still appears online and current, but the controlling Mac shows Connection failed and keeps reusing the revoked remote-control client enrollment. There is no visible UI action to reset/regenerate that controller authorization.
What steps can reproduce the bug?
Set up Codex Desktop remote control between two Macs.
From the controlled Mac, revoke access for the controlling Mac.
On the controlling Mac, go to Settings → Connections → Control other devices.
Try reconnecting to the controlled Mac.
Observe that the controlled Mac is visible, online, and on the current version, but the connection fails.
The row’s Delete action is disabled because the remote environment is online.
Toggling the connection, refreshing, restarting Codex, and rebooting do not regenerate the controller enrollment.
What is the expected behavior?
When the backend returns that the remote-control client has been revoked, Codex should clear the local revoked enrollment and create a fresh controller enrollment, or expose a Reset authorization / Reauthorize this device button in the Connections UI.
Additional information
The app log showed:
Remote-control client has been revoked
POST /backend-api/codex/remote/control/client/refresh/start returned 403
The workaround was to fully quit Codex and remove the revoked entry from:
~/.codex/.codex-global-state.json
Specifically under:
electron-remote-control-client-enrollments
After removing the stale client enrollment, Codex created a fresh one on launch and the Mac mini connection worked again.