{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihjw4i4lscv2xu2hkndjxqkk54gm6l7ugvmxttrvidptpuaj6vuay",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mohf6k5e2i62"
  },
  "path": "/t/again-codex-client-auth-forces-whatsapp-code-to-a-dead-number-but-chatgpt-codex-web-log-in-fine/1383951#post_1",
  "publishedAt": "2026-06-17T02:57:51.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "Codex client auth forces WhatsApp code to a dead number — but ChatGPT/Codex web log in fine - Codex - OpenAI Developer Community"
  ],
  "textContent": "# This is the background:\n\nCodex client auth forces WhatsApp code to a dead number — but ChatGPT/Codex web log in fine - Codex - OpenAI Developer Community\n\nAfter that ticket was resolved, I was able to log in to Codex without having to verify my originally registered phone number. However, the same issue has occurred again today and is now preventing me from logging in to Codex！！\n\nAs mentioned in the previous ticket:\nEither Codex should completely stop using the original registered phone number for login verification and instead use the SMS method configured under MFA, or OpenAI should provide a way for users to update the original registered phone number.\n\nIt seems you do not do anything to improve the process!\n\nIt is very difficult for me to keep using your service while constantly worrying that they may be locked out of my accounty.\n\nmy openai account: [redacted]\n\nEason\n\nThanks",
  "title": "Again -- Codex client auth forces WhatsApp code to a dead number — but ChatGPT/Codex web log in fine"
}