{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifg2xl4s5uvf6w2fs5qmdwz3ccl6pqkqigrrf2ddudmppstgpuf6q",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnej4ttghro2"
  },
  "path": "/t/codex-client-auth-forces-whatsapp-code-to-a-dead-number-but-chatgpt-codex-web-log-in-fine-case-09491223/1382372#post_9",
  "publishedAt": "2026-06-03T06:41:43.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@OpenAI_Support",
    "@owallesun"
  ],
  "textContent": "Update: as of now I can sign in to the Codex client with no verification prompt at all — it just logged in. Not sure if this was a backend fix on OpenAI’s side or something else changed, but the blocking phone-verification step is gone for me right now.\n\nThat said, the dead +44 number is still attached to my account, so I’d still appreciate the security/eng team unlinking it or replacing it with a valid MFA method, so this doesn’t resurface if my session expires or I switch devices. Case 09491223. Thanks @OpenAI_Support — and hope this resolves for @owallesun and others too.",
  "title": "Codex client auth forces WhatsApp code to a dead number — but ChatGPT/Codex web log in fine (Case 09491223)"
}