codex - 💡(How to fix) Fix Codex Desktop remote control remains connected but unusable after remote device revoked permission, and cannot be deleted or re-authorized

Body: I have two Codex Desktop/App Server devices signed into the same ChatGPT account.

Device A: macOS 26.4.1, Codex Desktop 26.513.31313, bundled codex-cli 0.131.0-alpha.9 Device B: gaoshaoyudeMac-Studio.local, app-server 0.131.0-alpha.9

What happened:

1. Device A could previously control Device B from Settings > Connections > Control other devices.
2. On Device B, access/permission for Device A was revoked by mistake.
3. After that, Device A still shows Device B under “Devices you can control from this Mac” as connected/online.
4. Trying to connect no longer works.
5. The UI does not allow me to delete Device B because the remote-control environment is still reported as online.
6. I also cannot force a clean re-authorization flow from Device A.

Observed diagnostics:

• GET /codex/remote/control/environments returns Device B as online: true.
• Device B appears as client_type CODEX_CLI / CODEX_DESKTOP_APP app-server 0.131.0-alpha.9 depending on the environment.
• Local state contains selected-remote-host-id and added-remote-control-env-ids for the stale remote-control environment.
• Clearing local state did not resolve the problem, so I restored it.

Expected behavior: After a remote device revokes controller permission, the controlling Codex app should either:

• show that access is revoked and provide a re-authorize flow, or
• allow removing the stale remote-control device locally, even if the remote environment is still online.

Actual behavior: The device remains shown as connected/online, but control does not work, and there is no apparent way to delete or re-authorize it from the UI.

Please advise whether there is a supported command or UI flow to revoke/reset a remote-control client enrollment and re-authorize the device pair.