Repository navigation
Change rate limit accounting #4217
Description
What feature would you like to see?
Why are the weekly limit and the 5-hour limit so close to each other? I would like to ask you how you plan to compete with Claude Code? I don't think it's necessary for me to subscribe.
Are you interested in implementing this feature?
No response
Additional information
No response
Activity
239573049 commentedon Sep 25, 2025
That is to say, if we exceed the 5-hour limit twice, I won't be able to use Codex this week.
wang0663-pixel commentedon Sep 25, 2025
Here’s the translation:
On Windows, MCP support is really poor.
You hit the weekly limit after only a few uses.
The CLI optimization is terribly bad.
Especially with the Team version—you hit the red line (quota cap) after just a few tries. This is, in my view, the most ridiculous subscription I’ve ever purchased!
wang0663-pixel commentedon Sep 25, 2025
“At a price of several hundred dollars, yet I can use it for less than a day each week—are you robbing me? And how are you even supposed to compete with CLAUDE?”
russeg commentedon Sep 25, 2025
They are close because the weekly limit is VERY VERY LOW.
There is no point to using Codex. It is basically a tech demo to keep them in conversation since Claude Code is all that was being talked about.
Claude Code has way more value and much better in every way.
looper200 commentedon Sep 25, 2025
For my tests
5h limit x 3 ≈ 1 weekly limitits very lowadsqx commentedon Sep 26, 2025
I described what it probably stems from.
2spring commentedon Sep 27, 2025
They are not close to each other even if they would show the same number lets say 34% , one is 34% of weekly (bigger amount) usage, other is 34% of 5 hrs (less amount of something) . Results are still not same , because totals of those 5hrs and weekly usage limits are not same.
Just 2 independent metrics there. no proportion between them. You can see 5 hrs limit is 99% and weekly is still 39% .. Or do you mean something different ?
adsqx commentedon Sep 27, 2025
The point is that the ratio is stated at the top and clearly described as 1:3, not 1:1.
No one claimed it was 1:1 — it’s explicitly explained why the ratio is low and not equal.
So, what you’re saying is both true and not true at the same time.
It depends on the ratio, and as you can see, that ratio is low.
And this is caused not by the limit itself, but by token burn.
With the same limit, proper context management could increase the number of requests by 10x–50x without touching the limit thresholds.
My guess is that Claude has lower raw token limits, but better context management, which is why it achieves that effect.
So, to answer the original poster’s question: if they want to compete with Claude Code and others, they must improve their agent.
They simply can’t afford to burn through limits so aggressively — doing so would cost hundreds of billions of dollars in GPUs.
Send single messages and check /status after each one — you’ll see the cache size grow quadratically.
Originally, the problem was masked 7–9x(and that’s why the limits increased by that much), because they were recomputing the entire context at every iteration.
Now, the input only shows you the new tokens, but that just hides the issue, because cached tokens still cost money.
And at the scale of such an explosive growth, having cache 10x cheaper doesn’t really help much.
carlos-naranjo-aa commentedon Oct 4, 2025
Here is the thing. I purchase additional credits, that is ok and the cli version on wsl2 was using the credits. Now all of the sudden a hard limit that cannot proceed with the work i am doing even if i pay for it because of this weekly limit. The best part is that the cli says that the weekly limit will reset in 5 days. What you guys suggest i tell to my client that i have to wait 5 days because somebody decided for god knows what reason that i cannot even use the credits i paid for? I am using the tool for real work. Thank god there is competition. Last but no least i ask in the "support" chat and the AI (again) tells me that a human is going to take "days" to answer my query. So welcome to the AI blues. Hope that an OpenAI human is reading this. If i cant use my credits for the codex because that is what i buy them for I Want my money back so i can go to another provider and get the service. the best one is that the system is actually using my credits...
FJOQWIERMDNKFAJ commentedon Oct 4, 2025
I’m a Pro user. Right now, with a 5-hour limit, my weekly limit increases by 1% for every 2% used. If that’s the case, if I use up all the 5-hour sessions in a week, does that mean I can only use two sessions? This seems very different from the statement that you shouldn’t hit limits unless you’re doing scripting. I don’t do any scripting at all; I just keep one or two windows open and work slowly.
Asia1o1 commentedon Oct 5, 2025
that's crazy...
williamsmonster2008-sketch commentedon Oct 17, 2025
Just now I got suspended by weekly usage 100%，but my 5 hours usage are still 19%，I cant get the point... how did it happen and what's their calculation way?
dlukt commentedon Oct 20, 2025
Why is there even a 5h limit?
Why can't this be removed?
Also the weekly limit.
It makes no sense other than annoying users.
If we have a monthly contingent of tokens let us use all the tokens and be done with it for the month, or let up buy more.
But this 5h and weekly limit is BS.
adsqx commentedon Nov 1, 2025
https://blog.langchain.com/deep-agents/
That’s exactly what I was thinking and talking about.
https://blog.langchain.com/introducing-deepagents-cli/
[-]Why are the weekly limit and the 5-hour limit so close to each other? I would like to ask you how you plan to compete with Claude Code? I don't think it's necessary for me to subscribe.[/-][+]Change rate limit accounting[/+]CryptoDragonLady commentedon Dec 7, 2025
In two days ive managed to hit 77% of my weekly allotment. Leaving me out of luck for 5 days if i continue. Im a plus subsciber. Claude has no weekly limit. With claude I might hit my 5 hour limit more quickly, but it doesnt leave me empty handed for the better part of 5 days! A weekly limit, on top of a 5 hour limit, is a bit too limiting and assinine. This is bad business.
feedback17 commentedon Apr 25, 2026
I want to add another angle to this request.
The issue is not only that 5-hour and weekly limits may be inconvenient. The deeper problem is the mismatch between monthly billing and window-based entitlement.
Codex is sold as part of a monthly Plus/Pro subscription, but actual usage appears to be enforced through shorter windows such as 5-hour and weekly limits. If unused included usage does not roll over, project-based users may pay for a full month but only receive practical access to the remaining weekly/window allowance when they actually use Codex heavily.
This affects Plus and Pro users alike. Even if Pro provides higher multipliers, those multipliers appear to increase each usage window; they do not create a monthly bank of included usage.
I support the request for a monthly pool, or at least partial rollover within the billing month, unused-to-credits conversion, burst/project-based plans, or end-of-cycle grace usage.
CryptoDragonLady commentedon Apr 26, 2026
CryptoDragonLady commentedon Apr 26, 2026