Codex Mobile setup: Allow button is a no-op because app-server rejects `remoteControl/enable`

[manevrit21]

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

Codex CLI/runtime: codex-cli 0.137.0 Global npm package: @openai/codex@0.137.0 Codex App version: unknown / not shown in this report

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows 11, Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

In Codex App on Windows 11, the Codex Mobile setup screen asks:

"Allow devices to control this computer?"

When I click the "Allow" button, the button visually clicks, but nothing happens. The setup screen does not progress, no QR/pairing flow appears, and no visible error is shown.

I checked the local Codex desktop logs after clicking the button. The UI appears to call remote-control methods, but the app-server rejects them as unknown methods/variants.

Relevant log lines:

2026-06-05T01:23:28.697Z error [electron-message-handler] Request failed ... method=remoteControl/status/read ...
Invalid request: unknown variant remoteControl/status/read, expected one of ...

2026-06-05T01:23:28.697Z error [electron-message-handler] Failed to read remote-control status

2026-06-05T01:23:52.882Z error [electron-message-handler] Request failed ... method=remoteControl/enable ...
Invalid request: unknown variant remoteControl/enable, expected one of ...

2026-06-05T01:23:52.883Z error [electron-message-handler] Failed to sync local remote control enablement

This looks like another desktop UI / app-server protocol mismatch: the Codex Mobile setup UI expects remoteControl/* methods, but the running app-server does not support them.

What steps can reproduce the bug?

1. Open Codex App on Windows 11.
2. Open Codex Mobile setup.
3. On the screen "Allow devices to control this computer?", click "Allow".
4. Observe that the button clicks visually, but the screen does not advance.
5. Check Codex desktop logs and observe remoteControl/status/read and remoteControl/enable rejected as unknown variants.

What is the expected behavior?

Clicking "Allow" should enable remote/mobile control and advance the setup flow, or show a user-facing error if remote control cannot be enabled.

Additional information

Related but not exact:

• Android ChatGPT remote connection to Windows Codex stuck on “Waiting for desktop…” #22733: Android waits for desktop / no incoming prompt
• Codex Desktop Windows crashes when clicking Settings > Connections > Connect computer #25194: Windows app crashes when clicking Connect computer
• Windows Desktop remote-control listener can stay on stale cached binary missing sandbox helper #25322: stale remote-control listener / cached binary issue

My case is different because the setup screen is visible and the "Allow" button is clickable, but it becomes a no-op because the running app-server rejects remoteControl/status/read and remoteControl/enable.