Repository navigation
ChatGPT desktop remote access failure #39907
Description
What version of the Codex App are you using (From “About Codex” dialog)?
OpenAI.Codex 26.818.3698.0
What subscription do you have?
200$ personal
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64 (windows 11 pro)
What issue are you seeing?
Subject: Android remote access cannot connect to ChatGPT desktop on Windows
I cannot connect to my Windows ChatGPT/Codex desktop app from either Android phone through the ChatGPT mobile app.
Phone error:
“Failed to connect to ChatGPT desktop. Make sure the ChatGPT desktop app is open, then try again.”
Timeline:
- Remote access worked during a long session yesterday.
- It disconnected during that session and has not reconnected since.
Confirmed: - The desktop app is open, updated, and signed in to the same ChatGPT account as both phones.
- Pairing succeeds, and the desktop app records the phone as recently connected, but the phone cannot load remote threads or establish an active connection.
- The issue occurs on two Android phones.
- The issue occurs over both Wi‑Fi and cellular data.
- I restarted the laptop, removed and re-created a phone pairing, and signed out and back in to the desktop app; none resolved it.
- No active Windows VPN was found.
- Windows Firewall has an enabled outbound Allow rule for ChatGPT.
- OpenAI’s status page showed no declared system-wide incident during testing.
Technical environment: - Windows 10 Pro
- Current Codex/ChatGPT desktop app: OpenAI.Codex 26.818.3698.0
- ChatGPT Classic 1.2026.190.0 is also running on the laptop. It has not been closed because it is not known whether it is relevant.
What steps can reproduce the bug?
Feedback ID: 01a023a7-8222-7ec1-a8f3-566f78afaf93
What is the expected behavior?
No response
Additional information
No response
Activity
github-actions commentedon Aug 21, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
nextConnectionCount=0) on 26.818.31338 #39856/wham/tasks/listreturns 503 #39815Powered by Codex Action
oysOYSoys commentedon Aug 21, 2026
I am experiencing the same symptoms. Android Remote pairs successfully, but the remote conversation fails to load and remains stuck in an endless loading/reconnecting state. Windows works normally.
charles1w commentedon Sep 10, 2026
We reproduced this “paired, desktop running, but no task list” symptom on another Windows/Android setup. The cause was slow task discovery: the host reads large helper-agent histories before excluding those agents from the list.
A history-preserving workaround that keeps inactive helper files out of the scan reduced listing from over 25 seconds to about 1.2 seconds, and the phone loaded tasks. The recommended app fix is to use the existing fast task index and filter excluded agents earlier.
Evidence, workaround and recommendation; related prior report: #36416. This is a possible match here if host logs reach
initialize -> thread/listand then stall; pairing failures and failures after the list loads need separate diagnosis.