Field report · OpenAI · Anthropic · Android
ChatGPT couldn't pair with ChatGPT. It took Claude to find out why.
My phone and my laptop were signed into the same ChatGPT account. Pairing them for Codex Remote went in circles: scan, sign in, approve, and straight back to the start. ChatGPT wouldn't look into its own app. So Anthropic's Claude plugged into the phone over USB, read its logs, and in under an hour pinned the loop on a known bug in ChatGPT for Android and found the update that fixes it.
Resolved Fixed by ChatGPT Android 1.2026.272 Diagnosed by Claude Updated 2026-10-03
ChatGPT wouldn't look at itself
The obvious first move was to ask ChatGPT what was wrong with ChatGPT. It wouldn't go there. So the job went to the competition, which, to be fair, had a shell on my laptop and a USB cable to my phone. That was the second time in two days that an OpenAI tool came up empty and Claude didn't. More on that below.
Sign-ins that worked, then looped anyway
every recorded one, before the update
Time until the app gave up
from a successful sign-in to the app deleting its own pairing key
Times the laptop showed the phone
its pairing screen just kept waiting
Updates needed to fix it
ChatGPT for Android 1.2026.265 → 1.2026.272
The loop
Codex Remote lets the ChatGPT app on a phone drive Codex on a computer. You start pairing on the laptop, scan a QR code with the phone, approve, done. Mine went like this, over and over:
Same account on both devices. Same Wi-Fi. No error message anywhere. The laptop sat there waiting for a phone that never showed up.
Enter Claude, with a USB cable
Saturday, 13:04 UTC. A Galaxy S24 Ultra on a USB cable, a Windows laptop, and a very annoyed owner.
Claude was already running as an agent on the laptop. It installed Google's Android platform tools, I tapped "Allow USB debugging" on the phone, and it started reading. It went through the phone's system log, the ChatGPT desktop app's own logs, and the text on the phone's screen while I ran the loop four more times.
Then it split the case up. Parallel agents took one job each: the phone, the laptop, the accounts on both, and every public bug report it could find. Next came a round of skeptics whose only job was to knock each theory down. One theory survived.
Everything that wasn't the problem
Wrong account
Checked on both ends. The laptop app and the phone app are on the same personal ChatGPT account, and the Codex Remote confirmation page showed that account on every attempt I captured.
Old QR code
A code only 8 seconds old failed exactly like an 18-minute-old one.
Network
Same Wi-Fi and subnet, firewall rules allowing the app, clocks in sync. Pairing goes through OpenAI's servers anyway.
VPN
AdGuard's VPN covers Chrome but leaves the ChatGPT app out, and the step that fails runs inside the ChatGPT app. The browser sign-in, which does go through AdGuard, worked every time.
The smoking gun
Every time, the ChatGPT app made a fresh hardware-backed key called codex_remote_control_device_key and opened the browser sign-in. The sign-in succeeded and handed control back to the app. Then, 2.6 to 3.0 seconds later, the app deleted that key and showed "Authorize this phone" again. No crash and no error, just a quiet reset. Tapping the button started a brand-new sign-in, which is why the Google and passkey screens kept coming back. The log times below are UTC.
13:12:35.586 sign-in returns to ChatGPT (WebRedirectActivity)
13:12:38.560 keystore: delete_key codex_remote_control_device_key:<id>
13:12:56.304 sign-in returns to ChatGPT
13:12:59.074 keystore: delete_key codex_remote_control_device_key:<id>
13:13:14.194 sign-in returns to ChatGPT
13:13:16.989 keystore: delete_key codex_remote_control_device_key:<id>Claude matched that pattern to a stack of user reports on OpenAI's own Codex issue tracker, all against ChatGPT for Android 1.2026.265, the same version as my phone. The reports cover Samsung, Xiaomi, Vivo, Nothing and other phones, paired with Windows, macOS and Linux. One of them is titled "Android 1.2026.265 (27): Codex Remote repeatedly returns to 'Authorize this phone' after successful browser authorization". As of October 3, OpenAI staff hadn't replied in any of those threads, but users there reported that the 1.2026.272 beta, out since at least October 1, fixes it. Full evidence.
The fix
Join the ChatGPT beta in the Google Play Store and install 1.2026.272. The beta sign-up looked stuck on my phone, but it had gone through: Google Play approved me as a beta tester, and about fifteen minutes later the update appeared.
To be fair, the actual fix is OpenAI's: they shipped 1.2026.272. What ChatGPT didn't do was tell me that, or look at its own app to find out. How to get out of the loop yourself.
Not the first time
The day before, my OneNote had been broken for nearly three weeks. An OpenAI Codex session investigated and gave up. Claude then traced it to a preinstalled Intel driver that zeroes the IPv6 Flow Label partway through every connection, a defect Intel had been told about in 2025. That one is documented at Intel ICPS breaks IPv6, OneNote and Microsoft 365.
October 2
Codex gave up on a broken OneNote. Claude found the Intel driver behind it by 15:21 UTC.
October 3, 14:24 UTC
ChatGPT wouldn't look into its own pairing loop. Claude pinned it on a known bug and found the update that fixes it.
Two OpenAI dead ends, two Anthropic diagnoses, solved on October 2 and October 3.
Seeing this too?
Check your ChatGPT version first. If it's 1.2026.265, follow the fix. If you're on 1.2026.272 or newer and still looping, add your phone model, Android version, ChatGPT version and computer to the tracking issue or to openai/codex#48777. Don't post email addresses, account IDs or codes.