After 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！！
As mentioned in the previous ticket:
Either 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.
It seems you do not do anything to improve the process!
It is very difficult for me to keep using your service while constantly worrying that they may be locked out of my accounty.
This is the codex verify page, the number is the original regirsted phone number which is dead now.
OpenAI doesn’t need to rely on discounts to attract or retain customers. If you simply fix this flawed login process and address the issues that customers are reporting, you’ll be able to keep your subscribers. Otherwise, you may lose another paying subscriber next month.
We’ve applied a mitigation for the Codex phone-verification loop on your account. Please try signing in to Codex Desktop or CLI again.
If you are still redirected to verification for the old phone number, please reply with the exact time and time zone of the attempt, along with whether you used Codex Desktop or CLI, and we’ll continue investigating.
Thanks again, Jordon. This solution feels more like a temporary workaround rather than a proper permanent fix.
The blocking verification page is no longer showing up for now; I just hope it won’t reappear later down the line.
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
What about everyone else? There’s a major issue with this that affects many with exactly the same underlying cause. Would you please take a moment and let the community know what (if anything) is being done?
I’m experiencing the known Codex phone-verification loop bug
(reported in community thread 1382387 and 1383951).
Codex CLI forces SMS verification to [redacted]— a
Brazilian number I have never owned. ChatGPT and all other
OpenAI services work normally on the same account.
Account: ChatGPT Plus, created Dec 2022
Login: Email OAuth via [redacted]
Platform: Codex CLI (macOS), latest version
Please apply the per-account mitigation that Jordan mentioned
in the community thread. I can provide exact timestamps of
the failed login on request.
