{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib6h2y6pgbs5r4y55bvohht5x7uhanqps3vnqfdmythbxpxlzul44",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnewllo3e332"
  },
  "path": "/t/codex-client-auth-forces-whatsapp-code-to-a-dead-number-but-chatgpt-codex-web-log-in-fine-case-09491223/1382372#post_12",
  "publishedAt": "2026-06-03T09:42:16.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@OpenAI_Support"
  ],
  "textContent": "Quick question for @OpenAI_Support while I have your attention: would enrolling in **Advanced account security**(which disables email/SMS sign-in codes in favor of passkeys) reliably stop my account from ever falling back to phone verification on that dead +44 number? I’d like a permanent fix, but I want to confirm it won’t lock me out given my registered number is dead — and that passkeys fully replace the SMS path. Case 09491223.",
  "title": "Codex client auth forces WhatsApp code to a dead number — but ChatGPT/Codex web log in fine (Case 09491223)"
}