›_ Codex Issues
Codex Issues / #31387

Windows Codex Desktop cannot enable Remote Control (Pairing with ChatGPT mobile fails)

Open 💬 8 comments Opened Jul 7, 2026 by gentlexx
💡 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 (From “About Codex” dialog)?

Codex 26.623.x（MSIX）

What subscription do you have?

PULS

What platform is your computer?

  • Windows 11 - ChatGPT Plus - Latest Codex Desktop (Microsoft Store version) - Latest ChatGPT mobile app - Same OpenAI account on desktop and mobile - Same Personal workspace

What issue are you seeing?

Environment

  • Windows 11
  • ChatGPT Plus
  • Latest Codex Desktop (Microsoft Store version)
  • Latest ChatGPT mobile app
  • Same OpenAI account on desktop and mobile
  • Same Personal workspace

Problem

Codex Desktop works normally for chatting.

However, enabling Remote Control always fails.

Steps:

  1. Open Codex Desktop
  2. Settings
  3. Connections
  4. Control this computer
  5. Click "Allow"

Result:

The button shows a loading spinner for about 5 seconds.

Then it displays:

"Unable to enable remote control. Please try again."

Previously, before reinstalling, another message appeared:

"Could not enable remote control. Please ensure only one instance of Codex is running."

After reinstalling, this message disappeared, but Remote Control still cannot be enabled.

What I have already tried

  • Reinstalled Codex
  • Reset the application
  • Verified only one Codex instance is running
  • Checked PackageFullName
  • Same OpenAI account
  • Same Personal workspace
  • Disabled VPN
  • Tried different VPNs
  • Latest ChatGPT mobile app
  • Latest Microsoft Store version
  • config.toml is normal
  • Windows Event Viewer shows no Codex crash or AppX errors

Chat works perfectly.

Only Remote Control cannot be enabled.

What steps can reproduce the bug?

Steps to Reproduce
Install the latest Codex Desktop on Windows from the official installer (Microsoft Store version).
Sign in with the same OpenAI account that is used in the ChatGPT mobile app.
Open Settings → Connections.
Under Control this computer, click Allow.
Wait approximately 5 seconds.
Actual Result

A loading spinner appears for about 5 seconds, then the following message is displayed:

Unable to enable remote control. Please try again.

No pairing code is generated, and the ChatGPT mobile app cannot connect to the computer.

Expected Result

Remote Control should be enabled successfully, and a pairing code should be displayed so the ChatGPT mobile app can connect to the Codex Desktop.

What is the expected behavior?

_No response_

Additional information

Additional Information

  • Windows 11
  • ChatGPT Plus account
  • Latest Codex Desktop (Microsoft Store version)
  • Latest ChatGPT mobile app
  • Desktop and mobile are signed in with the same OpenAI account.
  • Both are using the Personal workspace.
  • Chat functionality works normally.
  • The issue only affects Remote Control.
  • The application has been reinstalled and reset.
  • Only one Codex installation is present.
  • VPN disabled and multiple network configurations tested.
  • No Codex-related errors appear in Windows Event Viewer.

This issue is consistently reproducible on my machine after a clean reinstall and application reset.

View original on GitHub ↗

8 Comments

github-actions[bot] contributor · 13 days ago

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

  • #30372
  • #31161

Powered by Codex Action

Alpaca10086zyys · 13 days ago

I ran into the same issue! I tried uninstalling and reinstalling Codex, cleaning up some files, and using Activity Monitor to close other running instances, but none of it worked.

vuhnyuc2 · 10 days ago

Same here - please fix!

guyyst · 10 days ago

Some detailed error information would be nice here. My installation of the new Codex/ChatGPT app on a Windows 11 VM now just shows Pairing code unavailable: remote control pairing is unavailable until enrollment completes when attempting to add a device. Went through similar troubleshooting steps as OP with no luck.

An installation of the same Codex version on my main Win 11 PC show the QR code just fine.

<img width="534" height="813" alt="Image" src="https://github.com/user-attachments/assets/94883f76-a439-4464-b392-5548cbcbd03c" />

tinder-vasuhnyuck · 10 days ago
Some detailed error information would be nice here. My installation of the new Codex/ChatGPT app on a Windows 11 VM now just shows Pairing code unavailable: remote control pairing is unavailable until enrollment completes when attempting to add a device. Went through similar troubleshooting steps as OP with no luck. An installation of the same Codex version on my main Win 11 PC show the QR code just fine. <img width="534" height="813" alt="Image" src="https://github.com/user-attachments/assets/94883f76-a439-4464-b392-5548cbcbd03c" />

Stuck on the same step for windows 11 machine

guyyst · 8 days ago
Some detailed error information would be nice here. My installation of the new Codex/ChatGPT app on a Windows 11 VM now just shows Pairing code unavailable: remote control pairing is unavailable until enrollment completes when attempting to add a device. Went through similar troubleshooting steps as OP with no luck. An installation of the same Codex version on my main Win 11 PC show the QR code just fine.

The specific pairing error I was seeing here seems fixed for the Win 11 VM which was showing the issue before, despite still being on the same version from July 9th. So likely a backend issue which is now solved (at least for me).

iloveicedgreentea · 8 days ago

I get this issue too with a brand new install as of this comment. So frustrating

jaythornfield · 4 days ago

Same issue on Codex 26.707.12708.0 (MSIX, Windows 11 26200). Toggle turns on then flips off after ~2-10 seconds. Additional data points:

  • Reproduced with global proxy AND rule-based proxy — no difference
  • netstat capture during toggle shows NO blocked/SYN connection attempts, so it does not appear to be network-layer
  • codex remote-control start (npm CLI) fails with: "codex app-server daemon lifecycle is only supported on Unix platforms"
  • Chat and all other features work normally