{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigxcjylectysl56pbleh5c3poavaxs4wbj2fwzam4nq6jx4cohdyu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3moravzksq7e2"
  },
  "path": "/t/again-codex-client-auth-forces-whatsapp-code-to-a-dead-number-but-chatgpt-codex-web-log-in-fine/1383951#post_7",
  "publishedAt": "2026-06-21T01:24:45.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@OpenAI_Support",
    "auth.openai.com"
  ],
  "textContent": "Hi @OpenAI_Support / Jordan — same issue here, and it confirms this isn’t fully fixed. My earlier thread (Case 09491223) was auto-closed, but the problem just resurfaced for me too: my existing Mac session still works, but signing in on a new laptop (fresh client auth) again forces a WhatsApp/SMS code to my dead +44 number via auth.openai.com, with no way past it. Could you apply the same per-account mitigation to my account (Case 09491223)? Glad to provide exact timestamps + client details. Thanks",
  "title": "Again -- Codex client auth forces WhatsApp code to a dead number — but ChatGPT/Codex web log in fine"
}