You've hit your usage limit. Try again in 4 days 20 hours 9 minutes.
Resolved 💬 20 comments Opened Sep 7, 2025 by frankie0736 Closed Nov 18, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
Hi I'm on a business plan (30usd/month), purchased 2/3 days ago.
it stopped working after I use it for less than 20 hours.
what's the exact limitation while using codex?
is there any doc, thanks.
20 Comments
This is what's known so far
https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan
Pro
Local tasks: Average users can send 300-1,500 messages every 5 hours with a weekly limit.
I am pro user. what is the weekly limit? just worried every time see this info.
it will be better if i can check my usage somewhere. or it shows in vscode codex chat.
its not working. I have a pro plan an constantly get restricted. I always upgrade codex too. I dont use 1500 messages every 5 hours. now im maxed for 4 days this is silly.
I didn't send 1500 messages every 5 hours, that's insane...
I don't know why limit hit.
Everytime codex does something like for example searching / reading parts of your code...this counts as a message apperantly. not just prompts you send.
Dude, literally im Plus user with only around 10 prompts, and i hit the limit WHAT THE FUC?
At 200usd per month codex usage is 5% of what Claude code offers this is unfair
Hit the usage limit on pro. Odd. @aibrahim-oai @pakrym-oai assist?
I understand there are limits, but we need more transparency on what they are, how close we are to hitting them. I just got a 4 days cool down on my first week. Now I'm probably over using codex, but i much preffered what Antrophic does with Claude Code and has 5 hour block so at most you're banned for 5 hours. Or gives a warning when your usage is approaching limits and you get the opportunity to switch to a lower reasoning model to stretch it out.
I am a Business Plan user
Question regarding:
Business plan and Plus have the same
send 30-150 messages every 5 hours with a weekly limit.THEN why is the cooling period so long?
Did I miss somewhere where it may have mentioned "how many credits may have been per month?"
<img width="1101" height="508" alt="Image" src="https://github.com/user-attachments/assets/afdfd83f-e1e3-456d-9914-42176d4792ff" />
@MaurUppi well well i only prompted about 10-15 yet i got weekly limit already
not transparent enough, really dissapointed about this
amazing extensions yet not transparent :'(
not sure what is happening. i had to wait 3 days to use it then used it on and off today then i get:
🖐 You've hit your usage limit. Upgrade to Pro (https://openai.com/chatgpt/pricing) or try again in 1 hour 20 minutes.
i then wait over an 1 hour 30 minutes later and i get the following on my first try:
🖐 You've hit your usage limit. Upgrade to Pro (https://openai.com/chatgpt/pricing) or try again in 5 days 16 hours 23 minutes.
@phynias I had the same issue. I did some light coding, maybe 10-15 messages over the course of less than 3 hours, hit the usage limit, and went to sleep. Over 12 hours later, my first message gave me this message
<img width="861" height="95" alt="Image" src="https://github.com/user-attachments/assets/d6dc5811-0906-4304-8eb3-fa0fddefe43b" />
@Alfredo-Sandoval, may I know if there is any updated info to share?
@MaurUppi No. Just hit another weekly limit. its caching an insane amount of tokens and no idea why.
Token usage: total=748,177 input=693,709 (+ 9,781,504 cached) output=54,468 (reasoning 33,216)
Thanks for the responses.
What I felt confused about is that the measurement metrics on the webpage are
messagesorcredits, BUT actual practice is token calculation. I can't argue about this, but the user is expecting a more transparent and better UX experience. Such asbullllss""""" ■ You've hit your usage limit. Upgrade to Pro (https://openai.com/chatgpt/pricing) or try again in 5 days 22 hours 11
minutes. okey thanks ...
5 days, get lost greedy codex
@aibrahim-oai
May I know if the below is your mitigation plan?
https://github.com/openai/codex/pull/4075
Closing in favor of #6172