Logged in with ChatGPT Pro account, codex says "To use Codex with your ChatGPT plan, upgrade to Plus"
Resolved 💬 53 comments Opened Aug 15, 2025 by smat-dev Closed Dec 5, 2025
💡 Likely answer: A maintainer (vinhnx, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.21.0
Which model were you using?
gpt-5
What platform is your computer?
Linux 6.10.14-linuxkit aarch64 aarch64
What steps can reproduce the bug?
Started codex, entered "test" as a prompt.
Successfully ran codex login to refresh auth, no difference.
What is the expected behavior?
Codex works with ChatGPT login
What do you see instead?
🖐 To use Codex with your ChatGPT plan, upgrade to Plus: https://openai.com/chatgpt/pricing.
Additional information
<img width="1121" height="404" alt="Image" src="https://github.com/user-attachments/assets/ab97e467-f244-4782-8680-f5ad156dee8c" />
53 Comments
Having same issue with Plus membership
Having same issue, I thought my subscription is expired, but I have just subscribed recently
Same issue with my ChatGPT Plus account. I logged out and logged back in, still not allowed in.
Me too, Plus membership
Did you try revoking the the CLI key and regenerating? Just a thought.
https://help.openai.com/en/articles/11381614-codex-cli-and-sign-in-with-chatgpt
Pro plan, the same. Re-login does not help.
Update: The issue is resolved for me.
I’ve tried that, but it hasn’t worked.
For me Codex has started working again without any additional action taken.
I also have the same Issue on the Plus plan.
Even with the team plan, starting today it suddenly stopped working completely.
No matter how many times I log in again, it tells me to upgrade and I can’t use it.
But when I check with /status, it says my plan is “Team.”
<img width="1528" height="848" alt="Image" src="https://github.com/user-attachments/assets/a2adc72c-7193-4753-9356-85dbdd4417b8" />
same result!
me too and before that I was capped at 1 -2 messages on Plus.
Also gemini cli free tier allows much more back and forth requests with pro model before switching you to flash.
Edit: I use the latest version of codex.
gone after a 3-4hrs seem like limits, bun codex web works as expected
The same issue is occurring with my Codex as well.
I’ve tried various things, such as deleting the token, but it hasn’t improved.
same problem
Is it possible it's what happens when either the daily or weekly usage limit is reached? Since we're seeing it recover for some people and not others. I personally have two accounts, a work Teams account and a personal account, and I get the message on my personal account but not my teams account.
We're looking into this. The working theory is that the wrong message is being printed when rate limits are reached.
I've had this issue for roughly 20 hours. I think rate limits reset every 5 hours or so. If it was only a wrong message it should have been solved already, unless I'm wrong about the rate limit reset somehow.
I’m facing a similar issue. I’ve been experiencing this problem since last night. However, I just tried it again, and now I’m receiving this message: “🖐 You’ve exceeded your usage limit. Upgrade to Pro (https://openai.com/chatgpt/pricing), or wait for the limits to reset (every 5 hours and every week).” After trying it again, the message changed to ‘🖐 To use Codex with your ChatGPT plan, upgrade to Plus: https://openai.com/chatgpt/pricing.’ The last time I really used it was last night. It appears that the conversation is oscillating between those two messages. This issue is also occurring in version 0.22.0.
It would be great if the accurate message shared information something like "Your five hour period started x, and your one week period started y."
The message has changed to:
🖐 You've hit your usage limit. Limits reset every 5 hours and every week.
If I haven’t used it for over 24 hours but still get the above message,
does that mean I’ve hit the weekly limit?
With this message:
It’s way too unfriendly, and this makes it far too risky to rely on for work.
Checking the log, it seemed to be affected by TPM.
It claims to have used 40,000,000 tokens per minute.
However, I don't think that's possible.
If you are using MCP servers, deleting them may solve the problem.
I solved it. (But when I checked the status, it didn't seem to be using that many tokens.)
I had this issue as well, I was very confused. I bought tokens and set pretty high max budget but it doesn't seem to use the tokens even if i set the env. I'm able to use the web interface no problem, but constantly locked out of the cli app or get this message.
I suppose this can be closed now, since other issues cover questions about knowing when limits reset.
I just upgraded to plus and get this still after logout/login
@smat-dev may I ask why this issue is closed? I am on Team plan and it's literally saying I'm on Free plan.
Perhaps there are multiple causes
Same issue here, I upgraded my ChatGPT subscription to Pro and I get this. Tried re-logging in on Codex CLI but the error persists.
EDIT: Tried this morning after several hours (sleeping), it's now working. I guess there's a delay on the backend.
Same issue here
🖐 To use Codex with your ChatGPT plan, upgrade to Plus: https://openai.com/chatgpt/pricing.
▌ Explain this codebase
Ctrl+C again to quit
Got pro, get this message immediately
"To use Codex with your ChatGPT plan, upgrade to Plus: https://openai.com/chatgpt/pricing."
Using plus but got this error:: 🖐 To use Codex with your ChatGPT plan, upgrade to Plus: https://openai.com/chatgpt/pricing.
Tried revoking and adding a new key, still didn't work. Tried a config.toml and an auth.json file and it didn't work.
Same here. Recently upgraded to pro but it doesn't seem to have (immediately at least?) affected my usage limit.
Same here, so what reason for this terrible error still take a months to fix?
I just upgraded to the following version of codex, and I too get this error message "To use Codex with your ChatGPT plan, upgrade to Plus: https://openai.com/chatgpt/pricing." I've been on ChatGPT Plus for quite some time, and I ran codex like this:
codex --model o4-mini
@openai/codex@0.36.0
+1. Absolutely unacceptable. This should be a Sev2 for the auth team. Please treat this with urgency, people are paying but not receiving service.
Would you go to buy a ticket to enter the zoo, and then were told that you aren't allowed in because you didn't buy a ticket?
I've had the same problem. I solved it by completely removing codex and its configuration:
npm uninstall -g @openai/codexor brew uninstall codexrm -rf ~/.codexAnd it works for me. So just try "turn it off and on again" ;)
I’m experiencing the same issue, I have a Plus subscription, but it shows as Free.
I already tried changing the model, uninstalling and reinstalling, using the VS Code extension, and still nothing.
Same issue, any fixes?
I ended up completely removing codex (see @wysher post above), then rerunning codex but I had to force a login (for some reason codex doesn't automatically login). I ran it like this:
codex loginAfterwards, codex worked.
I removed everything and logged in again. didn't work
Headline: \$500B Stargate, \$0.05 Login Button
It’s wild: we’re apparently on the brink of funding a half-trillion-dollar interdimensional “Stargate” data center, yet Codex still greets me like, “Hi, Free User!” after three logins, two reboots, and a sacrificial USB hub.
If we can bankroll a server farm the size of a small moon, surely we can afford a login flow that remembers a Plus account for longer than a fruit fly’s lifespan. Right now it feels like the roadmap is:
I don’t need quantum compute—just a checkbox that stays checked. Until then, the only “gateway” I’m walking through is the one to yet another “Please upgrade to Plus” message.
codex login
Starting local login server on http://localhost:1455.
If your browser did not open, navigate to this URL to authenticate:
https://auth.openai.com/oauth/authorize?response_type=code&client_id=app_EMoamEEZ73f0CkXaXp7hrann&redirect_uri=http%3A%2F%2Flocalhost%3A1455%2Fauth%2Fcallback&scope=openid%20profile%20email%20offline_access&code_challenge=gufw8uzzrNt5d7wK9Qqt_4nJSv4WVPWREvJkl8pV41c&code_challenge_method=S256&id_token_add_organizations=true&codex_cli_simplified_flow=true&state=Ztf_bQvrS1io2qDNjupM9RRdAeYwAqP0HqP0XE2f3-8&originator=codex_cli_rs
Successfully logged in
📂 Workspace
• Path: ~
• Approval Mode: on-request
• Sandbox: read-only
• AGENTS files: (none)
👤 Account
• Signed in with ChatGPT
• Login: CodexBrokenButFunding500billionStarGate@gmail.com
• Plan: Free
🧠 Model
• Name: gpt-5-codex
• Provider: OpenAI
• Reasoning Effort: None
• Reasoning Summaries: Auto
💻 Client
• CLI Version: 0.39.0
📊 Token Usage
• Session ID: 0199737c-1d2d-7e43-bdaf-0705fb40cc20
• Input: 0
• Output: 0
• Total: 0
This worked for me, thanks.
Having the same issue. This solution did not work for me.
Also having this issue with Plus subscription
Fixed for me by waiting a day.
On Wed, Sep 24, 2025 at 6:56 PM Darin @.***> wrote:
Was happening to me, so I signed out of ChatGPT website and signed out of the VSCode extension, then I picked a different sign-in option: I picked "Sign in with Google" and it worked this time.
Kinda sucks how they're encouraging everyone to use one shared login for everything, this is basically Internet ID.
I solved this by editing ~/.codex/auth.json and setting "OPENAI_API_KEY" to a new value, which was null.
Mine was already null, but deleting the file and reauthenticating worked! (Even though relogging alone did not work)
This misreported plan is addressed by PR #7610. The fix will be in the next release (0.66). The underlying problem was that we were using the plan mode that was encoded in the cached access token. This can be out of date if you change plans. We now access the plan from a separate endpoint, so it's always fresh.
I have this problem. Status says I'm on Plus plan, but any command gives me this message. I deleted .codex folder to no avail. I'm on Windows.
"To use Codex with your ChatGPT plan, upgrade to Plus: https://openai.com/chatgpt/pricing"
Update: logout in browser didn't help, even though Codex did a re-login. But logout from Codex CLI did. It's working now.
same issue here
@Xaxupos, this bug report is closed. If you're seeing a similar issue with the latest version of Codex CLI, please open a new bug with details.