Android Remote cannot re-pair after removing a previously connected phone

What version of the Codex App are you using (From “About Codex” dialog)?

Codex App 26.803.10989.0; ChatGPT Android 1.2026.216

What subscription do you have?

ChatGPT subscription (Codex reports plan_type: prolite)

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64; Android 12

What issue are you seeing?

An Android phone previously paired successfully with this Windows PC through Remote. After I removed the phone from the desktop linked-device/Connections list, the same phone can no longer pair again.

Fresh QR codes are recognized by the Android app, but the app immediately reports:

配对失败
配对时出了点问题。请重新扫描二维码。
("Pairing failed. Something went wrong while pairing. Please scan the QR code again.")

The phone never reappears in the desktop Remote device list, which remains empty.

What steps can reproduce the bug?

1. Pair an Android phone successfully with Codex Remote on a Windows PC.
2. Remove the phone from the desktop linked-device/Connections settings.
3. Enable Remote and choose to add a device again.
4. Generate a fresh QR code.
5. Immediately scan the QR code from the ChatGPT Android app's Remote screen.
6. Observe the generic pairing failure on Android; the desktop device list remains empty.

This reproduces with multiple newly generated QR codes after restarting both apps.

What is the expected behavior?

A phone that was removed from the linked-device list should be able to pair with the same Windows PC again using a fresh QR code.

Additional information

Environment:

• Codex App: 26.803.10989.0
• ChatGPT Android app: 1.2026.216
• Desktop: Windows 10 x64
• Phone OS: Android 12
• Both devices use the same ChatGPT account and workspace

Troubleshooting already tried:

• Updated and restarted both the desktop and Android apps
• Confirmed the same account/workspace on both devices
• Generated and scanned multiple fresh QR codes
• Reset the desktop-side Remote identity/cache and restarted the app
• Confirmed normal ChatGPT login and chats work
• Confirmed the desktop can still generate Remote pairing sessions

The behavior suggests that removing a previously paired Android device may leave stale account-side registration/revocation state that blocks a new pairing claim.

Possibly related to #37925.

Could you confirm whether a removed Android device should be able to pair again, and check whether stale device registration or revocation state needs to be cleared server-side?

Start at the Remote pairing flow exposed by the desktop linked-device/Connections settings and the Android Remote QR-scan entry point. Trace what happens after a removed device scans a fresh code, then verify that the phone is restored to the desktop device list and that repeat pairing succeeds.