codex - 💡(How to fix) Fix Codex Desktop Remote Control authorization fails on account_user_id mismatch

Summary

Codex Desktop remote control authorization fails when using Settings > Connections > Control other devices > Authorize on chatgpt.com. The UI shows:

Failed to authorize remote control

The local Desktop logs show the actual failure is an account-user-id mismatch during remote-control client enrollment.

Environment

Codex Desktop: 26.513.20950 (2816)
Bundled CLI: codex-cli 0.131.0-alpha.9
Homebrew CLI: codex-cli 0.130.0
macOS app: /Applications/Codex.app
Date observed: 2026-05-15

The installed app verifies as signed/notarized:

/Applications/Codex.app: valid on disk
/Applications/Codex.app: satisfies its Designated Requirement
/Applications/Codex.app: accepted
source=Notarized Developer ID

Logs / Failure Signature

The UI-side log error is:

remote_control_authorize_failed errorMessage="Remote control enrollment start does not match current account."

The remote-control enrollment logs repeatedly show:

remote_control_client_enrollment_start_response
remote_control_client_enrollment_start_account_mismatch

The relevant fields appear to have this shape, with private ids redacted:

responseAccountUserId=user-...
tokenAccountUserId=user-...__<chatgpt_account_uuid>
tokenAuthUserId=user-...

So Desktop appears to compare the enrollment response's bare auth user id against the token's workspace/account-scoped account user id:

"user-..." != "user-...__<chatgpt_account_uuid>"

That produces:

Remote control enrollment start does not match current account.

Why this does not look like local SSH or duplicate local state

• Remote control from ChatGPT mobile to this Mac works.
• SSH to another Mac works.
• The other Mac has Codex installed and reachable through SSH.
• A duplicate local enrollment row was removed; local SQLite now has only one Codex Desktop enrollment row for the local Mac.
• The failed controller enrollment logs show hasExistingEnrollment=false and localEnrollmentAccountUserId=null, so deleting local enrollment rows does not seem to address this specific failure.

~/.codex/config.toml has:

[features]
remote_connections = true

codex features list reports:

remote_control                          under development  false

Request

Could you check whether Codex Desktop 26.513.20950 is incorrectly comparing response.account_user_id from /codex/remote/control/client/enroll/start against the token's chatgpt_account_user_id, instead of accepting the bare user_id / tokenAuthUserId form? Alternatively, should the enrollment endpoint return the workspace/account-scoped id?

No raw account ids, tokens, or full logs are included here, but the repeated failure signature is stable across multiple authorization attempts.