[Windows] Remote Control appears but enabling it always fails after several seconds

Open 💬 1 comment Opened Jul 31, 2026 by TT1228
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using?

  • Microsoft Store package: OpenAI.Codex_26.727.4816.0_x64__2p2nqsd0c76g0
  • About dialog/internal version observed: 26.727.40816

What platform is your computer?

Windows 11 x64.

What issue are you seeing?

Codex Desktop shows the Remote Control entry under Settings → Connections, but clicking Allow / Enable Remote Control waits several seconds and then reports that Remote Control could not be enabled.

The same behavior reproduces under a newly created Windows user with the same ChatGPT account, so this does not appear to be caused by one damaged Windows profile.

The mobile ChatGPT app has the Remote UI and can display a QR code / connection code, but the Windows host cannot complete the enable step.

Steps to reproduce

  1. Open Codex Desktop on Windows.
  2. Open Settings → Connections → Remote Control.
  3. Click Allow / Enable.
  4. Wait several seconds.
  5. The app reports that Remote Control could not be enabled.

Expected behavior

Remote Control should enable successfully and expose a usable pairing flow for the mobile app.

Diagnostics already collected

The local global state contains all expected migration/installation markers:

"remote-project-connection-backfill-completed": true,
"electron-local-remote-control-installation-id": "<redacted>",
"electron-remote-control-config-migration-completed": true,
"electron-local-remote-control-environment-id": "<redacted>",
"computer-use-bundled-plugin-auto-install-disabled": false

The bundled native assets exist inside the MSIX package, including:

app\resources\cua_node\bin\node_modules\@oai\cua\bin\windows\codex-computer-use.exe

The packaged app reports Status: Ok through Get-AppxPackage.

Relevant desktop log lines around the failure include repeated entries such as:

[electron-message-handler] chatgpt_pubsub_reconnect_scheduled ...
[devicecheck-attestation] DeviceCheck attestation unavailable ... errorCode=1
[statsig-refresh-diagnostics] ... A networking error occurred during POST request to https://chatgpt.com/ces/v1/rgstr ...

There are also many successful app-server calls with errorCode=null, including getAuthStatus, account/read, config/read, and thread/list, so the app is authenticated and the local app-server is responsive.

Troubleshooting already attempted without success

  • Restarted Codex and Windows.
  • Reinstalled the Microsoft Store app.
  • Re-registered the AppX manifest.
  • Recreated Codex global state.
  • Tested with a fresh Windows user.
  • Verified OAuth/ChatGPT authentication mode.
  • Verified the packaged computer-use runtime and native executable exist.

Impact

Remote Control is completely unusable. The UI provides only a generic failure message with no error code or recovery action, which makes diagnosis unnecessarily destructive and time-consuming.

Please add a specific error code and a supported diagnostics/export path for Remote Control enable failures.

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 27 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #35351

Powered by Codex Action