Skip to main content

Codex Asking for Phone Verification? Each Error and What to Do

Codex in the ChatGPT desktop app may require phone verification that email or an authenticator app can't replace. What each error means and the safe next step.

LaoZhang AI TeamPublishedUpdated 18 min read
On this page
Codex sign-in screen asking for phone verification, with safe next steps for each error

Codex can ask for a phone number even when ChatGPT on the web works without one, and paying for Plus or Pro does not remove the step. As of October 21, 2026, OpenAI's help article What does phone verification look like? says: "Phone verification is not generally required to create an OpenAI account or use ChatGPT. However, you may be asked to verify your phone number when accessing Codex in the ChatGPT desktop app." The same page adds that "Email or an authenticator app does not replace this required phone-verification step."

Codex is now built into the ChatGPT desktop app on Mac, Windows, and Linux; older posts call it "the Codex app." The Codex CLI and the IDE extension sign in through the same auth.openai.com pages, and GitHub reports show the https://auth.openai.com/add-phone screen in all three.

The short answers:

  • Without a phone number: once the prompt appears on a ChatGPT sign-in, there is no legitimate way past it, and device code login asks too. An API key avoids that screen, but your first API key needs its own phone verification.
  • Which number works: your own mobile number, by SMS. WhatsApp is offered in only 12 countries, not including the US. Landlines, VoIP, Google Voice, and premium numbers are rejected.
  • Old number you no longer have: OpenAI confirmed that sign-in bug on June 19, 2026 and shipped a change on July 22. Sign in again; if it still asks, reply in your support case.
  • Error messages such as "too many phone verification requests" each have their own next step and stop point, matched in the table below.

Can you use Codex without a phone number? Not with a ChatGPT sign-in

If the ChatGPT desktop app, the CLI, or the IDE extension sends you to add-phone or shows "Phone number is required," that account has to complete phone verification to use Codex with your ChatGPT plan. No setting, plan, or sign-in method turns it off from your side.

These have been tried and reported not to help:

  • Device code login. In GitHub issue #47419 (September 23, 2026, CLI 0.155.1), the user turned on "Enable Codex Device Code Authorization" in ChatGPT → Settings → Security and ran codex login --device-auth; it still required a phone number. Issue #45647 reports the same after a reinstall and an InPrivate window.
  • Upgrading. Pro (#25820) and Plus (#41795) subscribers report the same prompt.
  • Email codes or an authenticator app. OpenAI's help page says neither replaces the phone step.

What does work, depending on your situation:

  1. Verify with your own mobile number that can receive SMS. This is the only path OpenAI documents for the prompt.
  2. Use an Enterprise workspace if your company has one. OpenAI Support wrote on August 10, 2026 that "Phone verification is currently required for Business/Team users, while Enterprise users aren't subject to the same requirement" (OpenAI Community thread on enterprise Codex accounts). If an Enterprise SSO sign-in asks anyway, OpenAI's help page says to contact Support with the exact error.
  3. Sign in with an API key for local work. Codex accepts printenv OPENAI_API_KEY | codex login --with-api-key, but usage is then billed at standard API prices instead of your ChatGPT plan, Codex cloud still needs a ChatGPT sign-in, and creating your first API key on platform.openai.com requires phone verification. If your employer issues you a key from its own OpenAI organization, your phone is not part of that step. The API-key section below covers the costs.

Codex on the web is a separate case. The reporter in issue #54604 says Codex Web kept working while the Windows desktop sign-in failed, and OpenAI's help page names only the desktop app. Codex Web runs cloud tasks, not the local app on your files, and an email-and-password account needs multi-factor authentication before Codex cloud opens.

If your own number is rejected for one of the reasons in the error table and you have no other mobile number of your own, the next step is a support case, not a rented number. The reasons are in the section on rented numbers and copied sessions.

Why ChatGPT can work while Codex asks

OpenAI treats Codex as a higher-security product than chat. On May 15, 2026, OpenAI Support answered the OpenAI Community question "Why does the Codex app now require a phone number during login?" by saying Codex "now requires stronger security than other features." The same reply listed possible reasons: "updated security policies, anti-abuse protections, regional/account changes, suspicious login detection or because certain features/plans now require a verified phone number."

That is a general list, not a rule you can check against your account. OpenAI has not published which accounts get asked, which signal triggers the prompt for a particular account, or whether it will stop asking. Reports start in late April 2026: GitHub issue #20161, "Phone number verification doesn't work," opened April 29 and collected 208 comments, including users who were asked after an SSO sign-in.

In October 2026 OpenAI wrote the Codex exception into its help article. ChatGPT itself still does not generally require a phone number, so the web app and the Codex sign-in can disagree on the same account without either one being broken.

What OpenAI officially says about phone verification

These rules come from OpenAI's help center and from OpenAI Support replies on the Developer Community. They apply to the Codex prompt and to other OpenAI phone checks.

RuleWhat OpenAI saysSource
ChatGPT account and use"Not generally required." Earlier versions of the page said phone verification was no longer required, and the other-language versions still read that way as of October 21, 2026Phone verification help article
Codex in the ChatGPT desktop appYou "may be asked" to verify; email or an authenticator app does not replace itSame article
First API key on platform.openai.comRequired for the first key, not for later onesSame article
How codes arriveSMS, or WhatsApp where available; never email or a phone call. The country menu defaults to United StatesSame article
WhatsApp countriesAE, EG, ID, IL, IN, MY, NG, PK, SA, TR, UA, VN; US numbers get SMSWhatsApp verification country list
Number typesNo landlines, VoIP, Google Voice, or premium numbersOpenAI article on unsupported number types
Reusing a number"Up to 3 times," with no exceptions; deleting a consumer account frees the number after 30 daysOpenAI article on phone number reuse
Changing your numberNot offered, for ChatGPT or the OpenAI APIOpenAI article on changing your phone number
PlansRequired for Business/Team; Enterprise is not under the same requirementOpenAI Support reply, August 10, 2026

July 2026 board of OpenAI phone verification rules for ChatGPT accounts, first API keys, number reuse, delivery channels, and unsupported number types

This chart dates from July 2026 and predates OpenAI's October note about Codex in the ChatGPT desktop app, so its "Important context" box is out of date; the table above has the current rule.

Google Voice is a VoIP number, so it fails the same check: OpenAI lists it as unsupported and says those number types "are often associated with higher instances of fraud or abuse."

The 3-use article is written about first API key verification, and OpenAI has not said whether a Codex sign-in counts toward the same total. The "maximum number of accounts" message does appear in Codex sign-ins, though, so treat the cap as real.

Codex phone verification errors by exact screen text

Find the line that matches your screen. The screen texts come from OpenAI help pages or from user reports on GitHub and the OpenAI Community, linked in each row. OpenAI has not published how long any of these blocks last, so no wait time below is an official figure.

What you seeDocumented byNext stepStop and contact support when
auth.openai.com/add-phone, "Phone number is required"OpenAI help page; reports #43681, #47419Enter your own mobile number and pick SMSYour number is refused for a reason listed below
Number refused as a landline, VoIP, Google Voice, or premium numberOpenAI help pageUse a personal mobile number insteadYou have no personal mobile number
"The phone number you entered is invalid"User reports (no OpenAI page)Check the country code (the menu defaults to United States) and the full numberThe number is a real mobile number in a supported country and still fails
Your country code is missing from the selectorReport #43681 (+7 absent)None on that pageImmediately; check OpenAI's supported countries list first
"This phone number is already linked to the maximum number of accounts"OpenAI 3-use ruleUse another mobile number of your own, or sign in to the older account that holds the numberThe number is yours, new to you, and was probably recycled by your carrier
"Phone number already in use"Community report, October 16, 2026; #45647Sign in to Codex with the account that first verified the numberBoth accounts are yours and Codex still refuses
"You've made too many phone verification requests. Please try again later."Reports #25820, #52808Stop requesting codes; make one fresh attempt laterThat later attempt fails the same way
fraud_guard: "We've detected suspicious behavior from phone numbers similar to yours…"Report #41795Don't cycle through other numbersRight away, with the exact error
Asked to verify an old number you no longer haveOpenAI Support on the CommunitySign in to Codex againIt still asks; reply in your existing case
No SMS option, only WhatsAppOpenAI Support on the CommunityRefresh, re-enter the number, or try another browser or deviceSMS still doesn't appear
phone-otp/select-channel on a security-key-only accountReport #25737Nothing documented for keys aloneRight away; mention Advanced Account Security
username_already_exists on a phone-only account (phone-only signup is rolling out in the US)Report #54604If no email is linked, add one under Settings → Account → Email → AddThe email is already linked and the error repeats
Enterprise SSO sign-in asks for a phoneOpenAI help pageConfirm your workspace is Enterprise, not Business/TeamIt is Enterprise; send the exact error
platform.openai.com asks before your first API keyOpenAI help pageVerify by SMS or WhatsApp; later keys don't askYour number fails for a reason above

Recovery ladder matching Codex phone verification symptoms to safe next steps, things to avoid, and support evidence

The ladder dates from July 2026; it says not to retry blindly, and OpenAI still hasn't published how long a phone-verification request limit lasts.

"You've made too many phone verification requests"

This is a limit on code requests, not on Codex usage. In issue #25820 (June 2, 2026), a Pro subscriber's code never arrived; resending produced "You've made too many phone verification requests. Please try again later." and the block persisted after waiting. In issue #52808 (October 10, 2026), a Windows user saw "You have requested phone verification too many times" after clicking once.

OpenAI does not publish how long the limit lasts, so stop pressing Resend. Come back later, make one clean attempt, and if it fails the same way, note the exact time and time zone and contact support. Codex usage limits are a different system, covered in the Codex weekly limit reset guide.

"This phone number is already linked to the maximum number of accounts"

OpenAI says a number "can only ever be used for phone verification up to 3 times" and makes no exceptions. Its suggestions are another number or "accessing a previous account associated with your phone number." If you deleted a consumer ChatGPT account (not one banned for a violation), the number leaves the system 30 days later.

If you never used the number three times, your carrier may have recycled it. OpenAI's phone-only signups article says of a similar "Too many signups with this number" error: "Currently, there is no workaround. You would need to contact support."

"The phone number you entered is invalid" or your country isn't listed

First rule out the number types OpenAI refuses, then check the country menu: it starts on United States, so a number from elsewhere fails until you pick the right country. If your country code is not offered at all, as in issue #43681 with a +7 number, that page has no way forward. OpenAI's list of supported countries warns that access from outside them "may result in your account being blocked or suspended."

Old or inaccessible phone number: OpenAI's June–July 2026 fix record

If Codex asks you to verify a number you used years ago, OpenAI has confirmed the problem and changed something. GitHub doesn't show that: issue #25749 (72 comments) is still open with no OpenAI reply. OpenAI Support posted the record on the Developer Community:

  • June 3 and 5, 2026: Support said a problem sending verification codes to an old email address or phone number "has already been resolved" and asked anyone still blocked to email support@openai.com.
  • June 19: "We've confirmed a Codex client sign-in issue that can ask users to verify an old or inaccessible phone after normal account authentication succeeds." Support offered "an account-specific mitigation" while the broader fix was reviewed (Community thread "Locked out of Codex because of an old phone number?").
  • June 26: "We've resolved the original Codex phone-verification issue." Remaining reports "may have a different cause" and would be handled case by case.
  • July 22: "We made a change addressing an issue where Codex sign-in requested verification of an old or inaccessible phone number after you had already successfully signed in to your account. If this describes your situation, please try signing in to Codex again." (Community thread "Codex sign-in asks for phone verification on paid account")
  • July 15 to August 2: Support closed both threads and moved every case to individual support tickets, saying the reports included "several different sign-in and phone-verification issues."

What to do now:

  1. Sign in to Codex again from the ChatGPT desktop app or with codex login.
  2. If it still asks for the old number, reply in your existing support case. If you don't have one, contact support with the details listed below.
  3. Don't wait for a number-change option. OpenAI says it does not offer one for ChatGPT or the API.

New reports kept arriving after the July change. In September, issue #45647 describes Codex rejecting the user's existing number as already in use. On October 16, a Plus subscriber on the Community reported "Phone number already in use" for a current number tied to a second account they own, after an earlier fix had worked. OpenAI's June 26 note already said remaining reports may have a different cause, which is why each one goes through its own support case.

Device code, MFA, and SSO: none of them replaces the phone step

Device code. Codex's authentication docs say to enable device code login in your ChatGPT security settings first; the toggle is "Enable Codex Device Code Authorization" under ChatGPT → Settings → Security. Then codex login --device-auth gives you a code to enter at auth.openai.com/codex/device. It is the right method for a machine with no browser, explained in the Codex headless login guide, but it runs through the same account checks. Reports #47419 and #45647 show the phone step appearing on device login too.

MFA. An authenticator app does not replace phone verification, according to OpenAI's help page. Codex has a separate MFA rule: if you sign in with email and password, the auth docs say you "must set up MFA on your account before accessing Codex cloud." You may need both.

Security keys. In issue #25737, an account with Advanced Account Security and only FIDO2 hardware keys was sent to auth.openai.com/phone-otp/select-channel by codex login, while ChatGPT and platform.openai.com accepted the keys. No documented setting changes that, so this is a support case.

SSO. Business/Team workspaces are subject to phone verification and Enterprise workspaces are not, per OpenAI Support. An Enterprise SSO sign-in that asks anyway is one of the two cases OpenAI's help page tells you to report with the exact error.

If you came here looking for Codex on your phone rather than phone verification, that is the Codex mobile app, which controls a Mac or Windows PC from ChatGPT on your phone.

Developer route split: ChatGPT-plan Codex vs API-key Codex

An API key changes how Codex bills and what it can do. It is not a way to keep using your ChatGPT plan without verifying.

ChatGPT sign-inAPI key sign-in
BillingIncluded ChatGPT plan credits"Standard API pricing"
Phone stepMay be asked in the Codex sign-inAsked once, when you create your first API key
Codex cloudAvailable"Codex cloud requires signing in with ChatGPT"
Features tied to ChatGPT sign-inAvailableSome "limited or unavailable"
Commandcodex loginprintenv OPENAI_API_KEY | codex login --with-api-key

The Codex auth docs say that with an API key, "some features that rely on ChatGPT workspace access or cloud services are limited or unavailable." One you may hit is unsupported Codex auth method: apikey. In GitHub issue #45317 (September 14, 2026), the Codex desktop app's Chrome integration rejected API-key sign-in with exactly that message when asked to list or read browser tabs; a later comment reproduced it on macOS on September 19. Normal Codex work kept running. The message is not a phone error. It means that feature needs a ChatGPT sign-in, and the fix is to sign in with ChatGPT or work without that feature. Browser and computer control are covered in the Codex Computer Use guide.

Before switching, compare costs in Codex API key vs subscription and track spend with the Codex token usage guide. If the key returns 401 after you switch, see Codex 401 Incorrect API Key. A sign-in failing with "token exchange failed" is a different problem, covered in Codex Token Exchange Failed 403.

Why rented numbers and copied sessions make it worse

Temporary or rented SMS numbers, virtual numbers, bought or shared accounts, and auth.json or session files copied from someone else can get you past one screen. They leave you stuck at the next one.

  • Rented and virtual numbers often fail outright. OpenAI rejects VoIP and Google Voice numbers, and a rental gives you no way to check what kind of line you're getting.
  • You may be asked for the same number again. The old-number cases above show Codex asking for a number verified long ago. A one-time rental can't receive that code, and OpenAI does not let you change the number afterwards.
  • Shared numbers burn the 3-use cap for whoever owns them next, and for you if you ever need a new account.
  • Bought accounts and copied sessions aren't yours. Whoever sold or shared them can reset the password, see your work, or lose the account, and you can't show support that the account is yours.
  • Verification codes belong on OpenAI pages only. Enter the code from OpenAI's text message on auth.openai.com and nowhere else. A site or person that asks you to forward it is trying to take over the account.

OpenAI Support's own advice in the Community threads was to keep account details off public posts: "Please do not post your email address, phone number, verification codes, or other personal information publicly."

How to prepare a support case

Run the basic checks OpenAI Support suggested on June 5, 2026 first: sign out and back in, try a different browser or a private window, clear cache and cookies, and make sure you are signing in to the right account with the right provider (Google, Apple, Microsoft, or email). If the prompt is still there, write to support@openai.com, or contact Support through the Help Center using your account's email address.

Include what OpenAI Support asked for in the Community threads:

  • the exact time and time zone of one fresh sign-in attempt
  • whether you used Codex Desktop, the CLI, or device login
  • the screen or error you see, copied exactly; for the CLI, the codex-login.log file that codex login writes to your log directory
  • which situation you're in: old number you can't reach, current number refused, request limit, or fraud_guard
  • your plan and workspace type: Free, Plus, Pro, Business/Team, or Enterprise
  • your existing case number, if you have one

Leave out your full phone number and any verification codes. If you already have a case, reply in that case instead of opening a new one. Duplicate tickets split the history.

Once you're back in, add an email address if the account was created with only a phone number, and keep MFA on.

FAQ

Can I skip Codex phone verification?

No. Once Codex shows the phone step on a ChatGPT sign-in, OpenAI documents no way to skip it, and device code login, email, and authenticator apps don't replace it. The alternatives are an Enterprise workspace, which OpenAI Support says isn't under the same requirement, or API-key sign-in, which is billed at API prices and needs a phone for your first key.

Can I use Google Voice, VoIP, a landline, or a premium number?

No. OpenAI's help center says it does not support landlines, VoIP, Google Voice, or premium numbers for phone verification. Use a personal mobile number that receives SMS, or WhatsApp in the 12 countries where OpenAI offers it.

Why does ChatGPT work but Codex asks for phone verification?

OpenAI applies stronger security to Codex than to chat. Its help page says phone verification is not generally required for ChatGPT, but you may be asked when accessing Codex in the ChatGPT desktop app. OpenAI has not published which accounts are asked or why.

Does Plus or Pro fix Codex phone verification?

No. Plus and Pro subscribers report the same prompt. OpenAI Support said in August 2026 that Business/Team users are required to verify, while Enterprise users are not subject to the same requirement.

Can an API key avoid the phone prompt?

Only partly. Signing in with codex login --with-api-key skips the Codex sign-in screen, but OpenAI requires phone verification for your first API key, usage is billed at standard API prices, Codex cloud needs a ChatGPT sign-in, and some features fail with unsupported Codex auth method: apikey.

Why isn't the Codex SMS verification code arriving?

OpenAI Support says SMS is the default and WhatsApp an optional alternative in some regions. If no code arrives, don't resend repeatedly: that can trigger "You've made too many phone verification requests." Check that the country code is right, make one attempt later, and contact support if it still fails.

Do the Codex CLI and the VS Code extension ask for a phone number too?

Yes, according to user reports. GitHub issues describe the same phone step on codex login, on codex login --device-auth, and in the Windows and Linux desktop app, and an August 2026 OpenAI Community thread reports it in the VS Code extension on a work account. OpenAI's help page names only the ChatGPT desktop app.

What if my old phone number is gone?

Sign in to Codex again first. OpenAI said on July 22, 2026 that it changed sign-in so Codex stops asking for an old or inaccessible number after you've already authenticated. If it still asks, reply in your existing support case or open one. OpenAI does not offer a way to change the number yourself.

Can I change the phone number on my OpenAI account?

No. OpenAI does not offer a way to change or update the phone number for ChatGPT or the OpenAI API. If the number on file is a problem, contact support.

What should I send to support?

Send the exact time and time zone of one fresh attempt, whether you used Codex Desktop, the CLI, or device login, the exact screen or error text, your plan and workspace type, and your existing case number. Never post your phone number, email address, or verification codes publicly.

Sources23

External pages this guide links to, in the order they appear. Last updated Oct 21, 2026.

  1. 1.What does phone verification look like?help.openai.com/en/articles/8983040-what-does-phone-verification-look-like
  2. 2.GitHub issue #47419github.com/openai/codex/issues/47419
  3. 3.Issue #45647github.com/openai/codex/issues/45647
  4. 4.#25820github.com/openai/codex/issues/25820
  5. 5.#41795github.com/openai/codex/issues/41795
  6. 6.OpenAI Community thread on enterprise Codex accountscommunity.openai.com/t/1389769
  7. 7.issue #54604github.com/openai/codex/issues/54604
  8. 8.OpenAI Community question "Why does the Codex app now require a phone number during login?"community.openai.com/t/1380984
  9. 9.GitHub issue #20161github.com/openai/codex/issues/20161
  10. 10.WhatsApp verification country listhelp.openai.com/en/articles/8983038-which-countries-do-you-support-for-whatsapp-phone-verification
  11. 11.OpenAI article on unsupported number typeshelp.openai.com/en/articles/8983024-can-i-use-a-premium-number-landline-google-voice-or-other-voip-phone-number
  12. 12.OpenAI article on phone number reusehelp.openai.com/en/articles/8983031-how-many-times-can-i-use-the-same-phone-number-to-complete-the-phone-verification-associated-with-an-openai-accounts-first-api-key-generation
  13. 13.OpenAI article on changing your phone numberhelp.openai.com/en/articles/9135134-how-to-change-the-phone-number-associated-with-your-account
  14. 14.#43681github.com/openai/codex/issues/43681
  15. 15.OpenAI's supported countries listhelp.openai.com/en/articles/7947663-chatgpt-supported-countries
  16. 16.#52808github.com/openai/codex/issues/52808
  17. 17.#25737github.com/openai/codex/issues/25737
  18. 18.phone-only signups articlehelp.openai.com/en/articles/10388702-phone-only-signups
  19. 19.issue #25749github.com/openai/codex/issues/25749
  20. 20.Community thread "Locked out of Codex because of an old phone number?"community.openai.com/t/1382387
  21. 21.Community thread "Codex sign-in asks for phone verification on paid account"community.openai.com/t/1381357
  22. 22.authentication docslearn.chatgpt.com/docs/auth
  23. 23.GitHub issue #45317github.com/openai/codex/issues/45317
OpenAI Codex March 2026 capability stack showing GPT-5.4, app workflows, security, and mini subagents
Developer Tools & Agents

OpenAI Codex in March 2026: What's New and What It Can Do Now

March 2026 was the month Codex started making sense as a full agent system rather than a loose collection of surfaces. GPT-5.4 became the new core model, GPT-5.4 mini changed cheaper task routing, Codex Security entered research preview, and the app made parallel agents, worktrees, skills, and automations much easier to use.

11 min