Repository navigation
Windows Codex Desktop cannot enable Remote Control (Pairing with ChatGPT mobile fails) #31387
Description
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:
- Open Codex Desktop
- Settings
- Connections
- Control this computer
- 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.
Activity
github-actions commentedon Jul 7, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Alpaca10086zyys commentedon Jul 7, 2026
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 commentedon Jul 10, 2026
Same here - please fix!
guyyst commentedon Jul 11, 2026
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 completeswhen 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.
tinder-vasuhnyuck commentedon Jul 11, 2026
Stuck on the same step for windows 11 machine
guyyst commentedon Jul 12, 2026
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 commentedon Jul 12, 2026
I get this issue too with a brand new install as of this comment. So frustrating
jaythornfield commentedon Jul 16, 2026
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:
codex remote-control start(npm CLI) fails with: "codex app-server daemon lifecycle is only supported on Unix platforms"molijeur-blip commentedon Jul 29, 2026
Additional reproduction on 2026-07-29:
This reproduces the same host-enrollment failure described in this issue on a newer Windows build.
NexD5701 commentedon Oct 10, 2026
Correction: My previous comment described a separate proxy/WebSocket issue affecting web access; it was not the mobile pairing-code fix shown here.
For the Windows MSIX case in my report, the decisive fix was setting the proxy environment variables before launching ChatGPT.exe. Starting the app from that PowerShell session passes those variables to the app process, and mobile remote-control pairing then worked:
Replace the proxy URL with the local proxy address and port in use, and use the full ChatGPT.exe path for the installed package version. The screenshot’s path is version-specific. The key is that ChatGPT.exe must inherit the proxy environment variables.
cryingman520 commentedon Oct 18, 2026
Working solution in my Windows + FlClash setup (2026-10-18)
I hit the same problem on the Windows ChatGPT/Codex desktop app: Settings → Connections → Control this PC → Allow repeatedly displayed "Unable to enable remote control. Please try again" (Chinese:
无法启用远程控制。请重试) and did not generate a pairing QR code.Environment
OpenAI.Codex, package version 26.1013.4894.0.127.0.0.1:7890.What worked here
I completely exited the running ChatGPT desktop processes, then launched the installed ChatGPT.exe from a PowerShell session with explicit proxy environment variables:
Replace
7890with your actual local HTTP/mixed proxy port. Close any old desktop instances first; otherwise an existing process may be reused without inheriting the variables. This changes only the launching PowerShell session's environment, not permanent Windows settings.Result: After relaunching this way, I was able to enable Remote Control and generate a pairing QR code. I subsequently paired an Android phone successfully, after resolving a separate Android web-auth issue by updating ChatGPT and Chrome and switching the phone's default browser from Edge to Chrome.
This confirms a working path in my environment, not a universal fix or proof of the underlying Windows failure mechanism. I did not need to reinstall the desktop application, reset app data, or enable TUN mode.