Remote pairing fails on multiple phones while Windows host is connected
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Description
ChatGPT Remote pairing consistently fails after scanning the QR code.
The Windows host successfully enrolls and connects to the OpenAI remote-control WebSocket, but the mobile app displays “Pairing failed.” The same failure occurs on two different phones.
Environment
Host OS: Windows
ChatGPT desktop app version: 26.903.71938
ChatGPT plan: Plus
Mobile devices tested: Two different phones
Same ChatGPT account and workspace used on desktop and mobile
Steps to reproduce
Open the ChatGPT desktop app.
Go to Settings → Connections → Control this PC.
Enable Remote Control and select Add.
Scan the newly generated QR code using the ChatGPT mobile app.
Complete the authentication process.
Actual result
The mobile app displays a pairing failure message and asks to scan the code again. No phone is added to the connected-device list.
Expected result
The phone should pair successfully and the Windows host should appear in the Remote section of the mobile app.
Troubleshooting already attempted
Updated the desktop and mobile apps
Restarted the desktop app and Windows
Reinstalled the mobile app
Tested both Wi-Fi and mobile data
Generated and scanned fresh QR codes
Verified the same ChatGPT account, workspace, and Plus subscription
Completed MFA/passkey configuration
Reset the locally persisted remote enrollment
Tested with two different phones
The host log showed the remote-control WebSocket reaching Connected on 2026-09-15 at 00:41:17 KST, but mobile pairing still failed.
Related shared session ID: 01a05fda-0b40-7f61-ac68-d36bbed860a2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Reproduce the QR pairing flow from Settings → Connections → Control this PC on Windows, then compare the host WebSocket connection with the mobile pairing result and use the shared session ID in the logs; done means a phone appears in the connected-device list.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100