Android ChatGPT app cannot connect to Codex Desktop on Windows
What version of the Codex App are you using (From “About Codex” dialog)?
Codex Desktop 26.527.31326 Windows package: OpenAI.Codex 26.527.3686.0 app-server: 0.135.0-alpha.1
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows 11 Pro, OS version 10.0.26200, x86_64
What issue are you seeing?
I cannot connect from the ChatGPT Android app to Codex Desktop on my Windows PC.
The Android app shows my PC in the Codex mobile device list, but when I select it, it fails with a message like "Could not connect to Codex Desktop".
The PC appears to be online from the backend side. I checked the remote control environments endpoint and it returned online=true, busy=false for this Windows Codex Desktop environment.
I also reset the local Codex remote-control enrollment on the Windows PC. This regenerated the environment/server IDs, but the Android app still cannot connect.
What steps can reproduce the bug?
- Open Codex Desktop on Windows.
- Open the remote control / Codex mobile pairing screen.
- Open the ChatGPT Android app.
- Go to Codex mobile / remote control.
- Select the Windows PC shown in the device list.
- The app tries to connect, then fails with "Could not connect to Codex Desktop".
What is the expected behavior?
The Android ChatGPT app should connect to Codex Desktop and allow remote control.
Additional information
Android device: NX769J
Android version: Android 14
ChatGPT Android app version: 1.2026.146
Computer name shown in Codex mobile: Yuu-roomPC
The Android QR code shown by Codex Desktop decodes only to:
com.openai.chat://codex/open
I also checked Android network traffic with a CONNECT proxy. The ChatGPT app connects to OpenAI hosts including:
- android.chat.openai.com:443
- ws.chatgpt.com:443
- ab.chatgpt.com:443
So the phone appears to reach OpenAI servers, but the remote control connection still fails.
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I’m seeing the same failure on a Windows host with Android ChatGPT.
Environment:
Observed behavior:
connectionCount=0during connection attempts.com.openai.feature.codexremote.impl.data.CodexRemoteSessionForegroundServicestarting when the user taps connect, so the mobile app is attempting to start the remote session.Things checked/tried:
codex doctoron the Windows host is clean for auth/connectivity: ChatGPT auth configured, websocket connects with HTTP 101, ChatGPT backend reachable, no proxy env vars.com.openai.chatgptappears allowed; no background/network restriction was found.This looks like the mobile app starts the Codex remote foreground service, but the Windows host never receives/creates the live remote session through the relay.
Additional data point: the same Windows host, same Codex Desktop install, same ChatGPT account/workspace, and same network setup works successfully from a Google Pixel 8 Pro, but fails from a Xiaomi Poco X7 Pro.
So in this case the Windows host/account/relay path is functional in general. The failure appears specific to the Xiaomi Poco X7 Pro / HyperOS / Android 16 device path.
Failing device details from earlier diagnostics:
2412DPC0AG/rodin_global1.2026.181com.openai.feature.codexremote.impl.data.CodexRemoteSessionForegroundService, but the Windows Desktop never creates a live session and stays atconnectionCount=0.Working comparison device:
Follow-up/resolution for my Xiaomi case: after uninstalling and reinstalling the ChatGPT Android app on the Xiaomi Poco X7 Pro, remote control started working on that device as well.
So for this specific case:
This suggests the failure may have been caused by stale/corrupted ChatGPT Android app state or stale Codex remote pairing/session state on the Xiaomi device, rather than the Windows host or account/relay path being fundamentally broken.
Potential workaround for affected Android users: uninstall/reinstall ChatGPT on the failing device, then pair Codex remote control again.
Uninstalling and reinstalling Android app did not work for me.
In my case, logging out of the android app, clearing the cache and trying again worked perfectly
My devices:
Step by Step:
I am not sure if clearing the cache and revoking previous access is necessary as I make this on the first try, but worked for me, hope you find success too