{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih7zwjznisc2iewx2zqgfc5o6tafr4qmtytzebo7dzdjxzecscdni",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mne3pko2rmj2"
  },
  "path": "/t/codex-client-auth-forces-whatsapp-code-to-a-dead-number-but-chatgpt-codex-web-log-in-fine-case-09491223/1382372#post_5",
  "publishedAt": "2026-06-03T02:39:55.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@OpenAI_Support"
  ],
  "textContent": "In fact, I think the latest Codex update may have introduced an incorrect verification logic. If it were verifying the “Text message” method configured under MFA instead of the original registered phone number, this blocking issue would not occur. Could you please raise the issue to your engineer? @OpenAI_Support",
  "title": "Codex client auth forces WhatsApp code to a dead number — but ChatGPT/Codex web log in fine (Case 09491223)"
}