openai / openai/codex

ChatGPT desktop remote access failure

Open
#39,907 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug connectivity remote windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source file, test, or deterministic reproduction beyond the Android-to-Windows remote-access failure. Start by reviewing the remote-access diagnostics associated with feedback ID 01a023a7-8222-7ec1-a8f3-566f78afaf93 and reproducing the pairing and connection attempts across Wi-Fi and cellular data. Done means identifying the failure and restoring remote thread loading or documenting a confirmed blocker.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, rust
Domain
desktop-dev, mobile-dev, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.