Authentication for Codex has literally broken
What issue are you seeing?
My authentication for Codex has literally broken.
I already set up a passkey, phone verification, and an authentication app, but after going through three or four layers of verification, it still asks me to enter a phone number.
The problem is that this is an old number from many years ago, and I no longer have access to it. That means I get completely stuck and cannot use the service at all.
What is the point of having passkeys and multiple authentication methods if the system still falls back to an outdated phone number I cannot access? That feels like a pretty impressive way to lock users out of their own accounts.
<img width="461" height="460" alt="Image" src="https://github.com/user-attachments/assets/db24b087-4505-48e4-840f-2ef2787463db" />
What steps can reproduce the bug?
- Start the Codex CLI authentication flow.
- Complete the available verification steps, such as passkey verification, phone verification, and authentication app verification.
- Continue through the authentication process.
- The flow eventually asks me to verify or enter a phone number.
- The phone number it expects is an old number from many years ago that I no longer have access to.
- Because I cannot access that old phone number, I cannot complete authentication and cannot use Codex.
What is the expected behavior?
The expected behavior is that Codex should use my current verified phone number for authentication.
In my case, the flow first asks me to authorize access. After authorization, it asks me to enter a one-time code. After entering the code, it then asks me to verify by phone.
However, the phone number shown in the Codex authentication flow is not the same phone number used when I log in to ChatGPT. It appears to be an old phone number from many years ago, possibly from a previous phone number update. I do not know where Codex is getting this number from.
At the same time, if I log in to ChatGPT directly and use phone verification, it correctly uses my current phone number. Only Codex suddenly shows this old phone number.
The expected behavior is that Codex should use the same current verified phone number as my ChatGPT account, or allow me to choose another configured authentication method instead of blocking me with an outdated phone number.
Additional information
please contact me directly at ningjunzhi85@outlook.com for further info! Thank you
35 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Both of my legitimate subscriptions are now requiring a second round of mobile phone verification. I am currently unable to log in to Codex.
This same has happened with me. Even creating a 2FA with a new number on chatgpt doesn't work. In my case, the number whose code was sent doesn't exist anymore and the OpenAi developer account doesn't allow to change the number, nor even get the code from the email...
@strauss-vasconcelos
2fa for some reasons seems to act seprated , than log in with phone
(likely because in the past openai allowed register using few phones , if you want to understand why)
, if you want you can use sign in with a google account - it seems to not give me the phone screen
<img width="570" height="782" alt="Image" src="https://github.com/user-attachments/assets/49eda876-3975-44c1-94ca-c9f5aaf6977d" />
try to login/sign in with your phone
no such thing , do you mean using an api key? Its calculated by your chatgpt subscription
(i believe if you using AZURE it falls to the category of api key / other instruction)
$ codex loginand then select (sign in with phone) Does it still happen?
i had the issue once, I had to sign-up with phone on (chatgpt.com) next I did (codex login) and sign in using phone --- next I added a new email (just dont make duplicate account to not get locked , by if you use 2fa is completely external to this"verification step" which is seperated )
alternatively if you still face the same issue (you can try to sign in with Microsoft you get to choose which option you want)
(sign in with google doesnt offer you which sms or whatsapp)
<img width="658" height="607" alt="Image" src="https://github.com/user-attachments/assets/ab97d5ff-48a2-4dd3-bd05-735179b4b3aa" />
<img width="598" height="527" alt="Image" src="https://github.com/user-attachments/assets/dfa345d0-2cf8-45c1-8815-b07dd53d9c1b" />
<img width="666" height="555" alt="Image" src="https://github.com/user-attachments/assets/79780aa6-df28-4ee7-b08d-a295191e29df" />
a. are you trying to sign in using chatgpt account
a.1 (are you clicking sign using my phone)
b. are you trying to sing in using SSO ?
<img width="1231" height="298" alt="Image" src="https://github.com/user-attachments/assets/3b8de71f-7b46-4858-b52e-bdf47e6069fb" />
@lijun9190
You mean you subscribed to Plus ? can you use `
codex login --device-authand report back to me, if it - headless login helped?
(reminder if you are a free user , its completely normal and by-design --- if you are able to use chatgpt.com after account creation --- its only when attempting to sign in to codex)
make sure you connected to the desired account and do `
codex login --device-authalternatively its specified in the documentation (how to preform the head-less login)
why? Im afraid maybe you made few duplicated accounts and cant choose
https://developers.openai.com/codex/auth#preferred-device-code-authentication-beta
<img width="1190" height="375" alt="Image" src="https://github.com/user-attachments/assets/c7bb9f92-c6f3-4235-8e6c-7e3126165901" />
----
IF NOT using device-auth/headless
try to click "log in with another account" --
and make sure you enter your desired account this way
<img width="596" height="537" alt="Image" src="https://github.com/user-attachments/assets/4d3870d2-75fa-468e-aff0-d017e188e973" />
@Mahkhmood9 Thanks for the suggestion. I tried
codex login --device-auth.After opening
https://auth.openai.com/codex/deviceand signing in with my Plus account, it immediately redirects me to the second mobile phone verification step. I never reach the page where I can enter the one-time device code.So device-auth/headless login does not help in my case. The issue is that Codex/OpenAI auth is asking for verification using an old phone number that I no longer have access to.
I also confirmed that I’m signing in with the correct accounts. I’ve attached screenshots showing that both of my ChatGPT Plus subscriptions are active. I can use chatgpt.com normally, but I’m blocked only when trying to sign in to Codex.
<img width="840" height="387" alt="Image" src="https://github.com/user-attachments/assets/0c89522a-b647-445d-967a-a9a12035d9a5" />
<img width="850" height="599" alt="Image" src="https://github.com/user-attachments/assets/65ea33e5-530c-4af9-b4ee-3c74e0eb57fe" />
The screenshots are in Chinese because my ChatGPT UI language is Chinese. They show active ChatGPT Plus subscriptions with auto-renewal dates: June 6, 2026 and June 17, 2026.
try use a friend for this --- maybe someone in singapore (or taiwan) or outside china (try to avoid numbers from hong kong and )
I know for a fact some people complain when you fill a phone you dont get SMS - it has to be with the quality of the phone number. some phones will refuse an sms , and some are not allowed (when asking you for a new phone)
notice for some places they make it mandetory to send you it WHATSAPP not SMS
as per
considering none of the option worked ,
openai has an email (support@openai.com) (they usally respond within a day or two)
send from your plus-account email and explain you cant log in to codex (im not a fan of opening support ticket , but you spent real money on your subscrbtion, and you can be a student under a minimum wage , [so a loss for you?] )
I still dont know , is that a verfication loop, or just 2fa/mfa issue?
another thing, your phone number is chinese/hongkong/macau?
@Mahkhmood9 Thanks for your help.
I contacted OpenAI Support, and they confirmed that they do not support changing or updating the phone number on an account. They also said phone verification cannot be completed through email or a phone call.
So the current situation is that unless I can regain access to the original phone number, this account cannot continue using Codex. The only workaround is to use another account that can complete phone verification with a supported mobile number.
I’m leaving this update here in case it helps others who run into the same Codex sign-in issue.
Thanks again.
Just insisit its a 2fa/mfa issue , in their email , insist over it ---
ask them to clear all of the phones in your account (before you say you want to change or updae the account)
insist on the fact that you are a paying user - and that its a simple function
(perhaps ask for a refund, or use your credit card provider) its not okay if you cant access a core product - you paid for
I recomend , make making a fresh new account on another number you wont loose easily (you say you are greated with another verification screen) (either you are willing to sacrfice the 20$ or got a refund )
Can you confirm its 2fa issue? or? a verifcation issue? (I know for a fact you can have 2 phones linked (1 for verifcation , 1 for 2fa ) )
I dont know of a screen that ask for to verify with the same number , unless its 2fa
again , if you are totally locked out of codex , I recomend taking a bold step, and make a new account (-> ONLY IF)
(optional attempting to get a refund, if with in a reasonable 14 days of the charge) and then pay on the new account.
as going to make back and forward emails with insisting over it would be a blunder and not a sacrifice
generally if you are a young student who is in university - I recomend accessing documentation when you a developer - depending and the level and technicallity you aim for. Chatgpt is a great source - but never neglecting written specification and documentation (also comes handy whats good if you ever need to create a product)
excel is nice, libreoffice is nice (if you like lightweight software)
again codex is the best on the market there is no reason , if you already lucky to be born with something as cool as AI out there.... and I dont want you to loose access to your account, if its a large investment for you
<img width="90" height="40" alt="Image" src="https://github.com/user-attachments/assets/77abb36c-bc19-4f27-8dfe-a72de8a45877" />
same problem(
same problem for me as well
Same problem here. ChatGPT Pro, ~3 years, Google login. ChatGPT web + app work fine — only Codex sign-in is blocked.
I pass the second factor by any method (Authenticator, push, SMS to my current number, email) — all succeed — and then a final "Verify your phone number" screen demands an OTP to a number I changed years ago and no longer control. No "try another method" on that screen. The old number isn't in my ChatGPT settings, and I even checked my Google account (recovery / account / 2-Step phones) — it's only my current number there too. So this legacy number lives only in OpenAI's backend, with no way to remove it.
What bothers me most: OpenAI effectively revokes your ability to use Codex if you ever changed your phone, while ignoring the fact that you have proper 2FA configured and pass every factor successfully. That feels like being cut off unilaterally despite proving account ownership.
And it's logically inconsistent: if this phone gate were truly a security requirement, why does ChatGPT itself keep working normally on the same account, and only Codex enforces it? Same account, same identity, same 2FA — one product trusts it, the other dead-ends. That points to a flow bug, not a real security need.
Support's answer was "make a new account" (case #09483835) — not acceptable for a paid 3-year account when I control every login factor. Please route this to account-security/engineering and give authenticated paid users a way to clear an obsolete phone step. Env: macOS, codex-cli 0.136.0; codex login and --device-auth both hit the same wall.
Same problem. I upgraded this account last week and didn't know the old number was used at all. Been years since I've had it.
I also troubleshooted Google-sign in if it received the number from there but Google was swapped awhile ago too.
It's a mess, only the auth needs the number, everything else is fine with passkey? I know that ChatGPT and Codex accounts are technically seperate from clawdbot days. Easier to keep vibe coded projects seperate than trying to merge them eh?
**Support is adamant that they are aware of the issue that some phone numbers are not receiving text messages. I am adamant that this has nothing to do with why I contacted them in the first place. They seriously keep replying this way no matter what I say, I wish I was kidding. It's painful and a real person supposedly btw. OpenAI is completely dodging this after I asked to remove all phone numbers to the account.
same problem.
same problem.
same problem.
same problem.
Text Message as an MFA method was even disabled before this happened.
Edit: Looks like it's fixed; authentication w/ AAS enabled no longer requires phone verification.
Please fix it
Tested - that is not working for me at least
same problem
same problem
I was able to log in! I believe they fixed it.
how did you log in, just randomly retry?
Yes, just another attempt. That time where was no that last window with old phone's OTP.
But I also submitted a ticket with OpenAI. They didnt' reply though
still the same problem for me
Same issue here. I tried log in with my password, passphrase, and Authenticator app, but I'm still being asked to verify via SMS to a UK phone number that I don't own. I'm based in Asia and have never used that number. As a result, I'm completely locked out from Codex. What is happening here?? Any help would be appreciated.
<img width="552" height="455" alt="Image" src="https://github.com/user-attachments/assets/5f8c5336-4e8a-4226-abe8-3f8fb911afc3" />
same problem. please fix!
same problem. please fix!
same issue
same issue!! how can i log in my codex? i need work and study ! please!
I think this is intended..
same issue
YES, OPENAI STOLE MY MONEY
THEY ALLOWED ME TO SUBSCRIBE WITH MY NOW-LOST NUMBER!!!
THEN CHANGED FLOW
REVOKED MY LOGIN
NOW CANNOT LOGIN
<img width="174" alt="Image" src="https://github.com/user-attachments/assets/8022481b-03c0-451c-a5be-0e20030cc386" />
<img width="154" alt="Image" src="https://github.com/user-attachments/assets/cdae6443-b985-4936-894b-bbdcde95f92b" />
<img width="135" alt="Image" src="https://github.com/user-attachments/assets/82078716-f69c-4fe0-96e2-6778026af7cb" />
you may want to censor your own phone number