Remote pairing fails between Windows Codex App and Android ChatGPT using both QR code and manual pairing code
Nobody has claimed this yet.
- 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)?
26.908.70816 (Windows package version: 26.908.9136.0)
What subscription do you have?
ChatGPT Pro — Personal workspace
What platform is your computer?
Windows 10 Pro 22H2, OS build 19045.4291, x64 PowerShell output: Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
Remote pairing between the Windows Codex App and the Android ChatGPT app consistently fails. Both QR-code pairing and manual 8-digit code pairing fail.
Environment
- Codex App version: 26.908.70816
- Windows package version: 26.908.9136.0
- Desktop OS: Windows 10 Pro 22H2, build 19045.4291, x64
- Android ChatGPT version: 1.2026.251
- Subscription: ChatGPT Pro
- Both devices use the same ChatGPT account and Personal workspace.
Steps to reproduce
- On Windows, open Settings > Connections > Control this PC.
- Enable Allow connections and click Add.
- Scan the QR code with the phone and proceed with pairing.
- Pairing fails in the Android app.
- Alternatively, select the Computer tab in the desktop pairing dialog, then enter the displayed 8-digit code in the phone's manual pairing screen.
- Manual pairing also fails.
Expected behavior
The phone pairs successfully, and the Windows host becomes available in Remote.
Actual behavior
The Android app displays:
“配对失败”
“配对时出了点问题。请重新扫描二维码。”
English translation:
“Pairing failed.”
“Something went wrong during pairing. Please scan the QR code again.”
No specific error code is shown on the phone.
Troubleshooting already completed
- Confirmed the same account and Personal workspace on both devices.
- Tested both QR-code and manual-code pairing.
- Switched the phone from Wi-Fi to mobile data. Normal ChatGPT conversations work, but pairing still fails.
- Restarted both apps and generated fresh pairing codes. The issue persists.
- Google Play currently shows Open rather than an Update button.
Desktop log observations
After restarting the desktop app, remoteControl/pairing/start requests completed with errorCode=null at approximately 11:37:24, 11:37:51, and 11:37:53 on September 17, 2026 (UTC+8).
These entries show that the desktop pairing-start requests completed without a reported error, but they do not explain why pairing fails on the phone.
Feedback ID
01a0ad64-ff0f-75b3-a9ea-ca6e0f864064
Please investigate the pairing failure. If more diagnostics are needed, please advise how to collect the relevant Android pairing error details.
What steps can reproduce the bug?
Feedback ID: 01a0ad64-ff0f-75b3-a9ea-ca6e0f864064
What is the expected behavior?
The Android ChatGPT app should successfully pair with the Windows Codex host using a valid pairing QR code or manual pairing code.
After pairing, the Windows computer should appear in Remote on the phone, allowing me to start or continue tasks.
Additional information
Possibly related to #35855, which describes a similar Windows/Android Remote pairing failure. I cannot confirm whether the root cause is the same.
This report reproduces the issue with:
- Codex App 26.908.70816
- Windows package 26.908.9136.0
- ChatGPT Android 1.2026.251
- Windows 10 Pro 22H2, build 19045.4291, x64
Both QR-code and manual-code pairing fail.
Recent reproduction: September 17, 2026, approximately 11:37 (UTC+8). Desktop remoteControl/pairing/start requests completed with errorCode=null, but the Android app displayed a generic pairing failure without a specific error code.
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 file or test is identified in the report. Start by reproducing QR-code and manual-code pairing with the listed Windows and Android versions, then inspect the desktop pairing-start observations and request Android diagnostics. Done means a valid pairing succeeds and the failure path provides actionable error details if it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- desktop, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100