codex - 💡(How to fix) Fix Codex App Remote Control setup fails due to account_user_id mismatch

What version of the Codex App are you using (From “About Codex” dialog)?

26.513.20950 (build 2816); bundled codex-cli 0.131.0-alpha.9

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

I am trying to set up Codex App Remote Control from my MacBook to a Mac Studio via Settings > Connections > Control other devices > Set up.

Both machines are signed into the same ChatGPT account and the same workspace, and I checked for updates in the Codex App; no update is available.

The setup consistently fails with:

Failed to authorize remote control

Based on local logs, this does not look like a Mac Studio reachability, SSH, firewall, Local Network, or macOS permission problem. The failure happens during the local Remote Control client enrollment authorization flow, immediately after the enroll/start response is received.

Relevant redacted log sequence:

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

The important mismatch is:

selectedAccountUserId = user-<redacted>__<account_id>
tokenAccountUserId   = user-<redacted>__<account_id>
tokenAuthUserId      = user-<redacted>

responseAccountUserId = user-<redacted>

So the selected account and token account user id agree with each other, but the enroll/start response returns the unqualified user-<redacted> form instead of the account-qualified user-<redacted>__<account_id> form. The client then rejects the response as an account mismatch.

What steps can reproduce the bug?

Feedback ID: 019e29b0-53da-75b2-8397-f7228557a772

1. Open Codex App on the MacBook.
2. Go to Settings > Connections.
3. Open the “Control other devices” tab.
4. Click “Set up”.
5. Continue the authorization flow.
6. Codex App shows Failed to authorize remote control.

This reproduces consistently. Both the MacBook and Mac Studio are signed into the same ChatGPT account/workspace. I also checked Codex App > Check for Updates, and no update was available.

The latest local log attempt showed:

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

What is the expected behavior?

The Codex App should complete the Remote Control client enrollment / authorization flow, then allow this MacBook to control the Mac Studio.

If the same ChatGPT account and workspace are selected, the app should treat the enrollment response as belonging to the current account even if one side uses the account-qualified user-<redacted>__<account_id> representation and the other side returns the unqualified user-<redacted> representation.

Additional information

Why I think this is a product bug rather than a local setup issue:

• The selected account and token account user id match each other.
• The server enroll/start response appears to use a different account user id representation.
• There is no stale local client enrollment in the failing flow (hasExistingEnrollment=false).
• Remote Control environments refresh successfully before the authorization attempt.
• The failure happens immediately after enroll/start response validation, before any meaningful Mac Studio connection attempt.

I also noticed repeated local log entries like:

unsupported feature enablement `auth_elicitation`
currently supported features are apps, memories, mentions_v2, plugins, remote_control, tool_search, tool_suggest, tool_call_mcp_elicitation

This may indicate a Codex App frontend / bundled app-server feature mismatch in this build.

This looks similar to #22696, which also reports Codex App 26.513.20950 failing in “Control other devices” with Failed to authorize remote control.

I can provide the full local Codex Desktop logs privately if useful.