Replies: 56 comments 80 replies
|
I'd definitely also appreciate some clarification on the codex-cli limits for the Plus plan |
|
ChatGpt Plus (GPT-5 Medium)
|
|
Now I'm wondering what that cap would be if we use the api pricing? Would it make more sense to have Plus and fall back to API or to use Pro |
📊 Token Usage
• Input: 1491682
• Output: 6819
• Total: 1498501ChatGPT Plus, one conversation, limit triggered. |
|
it's way too low. it did 6 tasks and then stopped mid task 7 of 9. btw those 7 tasks were base skeleton only, no implementation. teams subscription |
|
I'd really like to have a more clear info on how limits reset. It seems that I've hit weekly limit, and I have no idea when it will reset (Plus subscription). |
|
Would be nice to have a warning like how Claude Code does... "Approaching Usage Limit" or something like that. |
|
I am totally puzzeled. I got Plus. It seems that limits in the web codex and codex cli are totally seperate. I have never run into the limit in web codex. I just now ran into the limit in codex cli, but web codex still accepts prompts . |
|
Limits are better but still too low. |
|
I just hit the usage limits with Plus and I get this message.
Usually it was try again in 5 hours... Is there a new usage limit? |
|
What they're doing is borderline criminal. |
|
Last week I hit the 5h limit once, and the weekly limit on Sunday evening (had to wait 11 hours). Tokens do cost money and we can do things on our side to reduce usage ("cognitive load" for the LLMs):
Of course it depends on the project, but I'm trying to chunk my tasks in a way to have faster responses which usually means less tokens usage. |
|
I'm on the Plus plan and just started using Codex VSCode, first session. Worked fine for half a day, then I got the 5h limit and it asked me to wait for 30 mins. Fine with me, no problem, I have some other things to do anyway. So far so good. But one day later I hit another limit (this is only the second time I've hit any kind of limit), this time it asks me to wait for 5 days! 5 days, you gotta be kidding! Not a few hours, but 5 days! A tool quitting all of a sudden, out of the blue, for that long is crossing a red line for me. Totally unacceptable. I wouldn't mind waiting for a few hours, but waiting for days renders this tool totally unworkable in any practical setting. 5h limits are ok, but the weekly limits are nuts. Please fix the limits ASAP! |
|
Let me stick with CC |
|
I opened a feature request addressing some of the discussed issues in a different way: The proposal is to let Codex CLI continue a session after hitting plan limits by allowing re-authentication — entering a new API key or logging in with another account — instead of terminating. This would prevent losing context or leaving code in an inconsistent state. Vote for it if you like it. |
|
maybe they all going into price fixing |
|
new model
https://community.openai.com/t/codex-updates-mini-model-higher-limits-priority-processing/1365540 |
|
oh it just reset to 100% weekly, it said it would on 25th |
|
github santa doing his remote rounds early
…On Sun, 23 Nov 2025 at 12:19, Alex Hunt ***@***.***> wrote:
For me it said the next weekly reset was on 26th, the next day it did
reset itself and changed the date to Nov 30th.
—
Reply to this email directly, view it on GitHub
<#2251 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABU35VUL2V6FA4W5K4H4CD36GJ4HAVCNFSM6AAAAACDYMECQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBVGIYDSOI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Wtf is even the point if this stuff keeps hitting limits. What am I paying for. A broken product? If my toaster stopped working after 2 slices of bread, I'd throw it out. Maybe time to do the same with this AI slop. |
|
They reintroduced the enforced limits and lying about it. |
|
I purchased for 40$ additional credits after hitting weekly limit but the limit did not lift! I got 1000 "code review credits" which i do not want. Also unable to process refund for this |
|
limits are great now thx, i can keep 2 clients happy with just gpt + |
|
at 47% weekly usage, 53% of 5 hour rate limit, yet I'm still being rate limited... nothing better than shadow rate limiting my rate limit's rate limit I mean.... scream to me your infrastructure is unstably oversubscribed, without saying out loud, you know... go ahead and just bake that policy right on top of the RAG of your "support agent" and call it a day, am I right? It takes some seriously bad character to deliver half and then serve up the rest as a toast note. Could you imagine ordering a tomahawk steak and then they come out with tapas and toast? |
|
I noticed that my token usage seems to be significantly higher than before. The same tasks and prompts now appear to consume several times more tokens than they did previously. I did not change my workflow or prompt size. Has anything changed recently in how tokens are counted or how responses are generated (e.g. reasoning tokens, system prompts, or model behavior)? |
|
codex team, i'm not sure what's going, but the limits situation is a joke at the moment. it's totally unpredictable. in less than a day after the reset and i already ran out for the week (reset only takes place on the 18th), on the pro plan. do you guys know what could be happening? |
|
I had a weekend and didn't do anything for a couple of days (with 95% of limits). I thought I'd come back and use up my weekly limits for the last two days, and then start over. My limits were reset, so I came back from vacation and spent 75% of my weekly subscription in the first two days. It was kind of a joke. Maybe you could reimburse me somehow? Well, if you have something reset, try to keep people's limits, but give them a voucher to reset their weekly limits - that would be much fairer.. :( |
|
alguien a probado el pro? cual es el limite de esa suscripción? en la pagina dice ilimitado |
|
Great thread. To answer @shanecowherd's question about API vs subscription — here's the math based on current API pricing: GPT-4o API rates (per 1M tokens):
Example: Your typical Codex session
The break-even shifts once you:
For heavy Codex CLI users who also use other LLM APIs (Claude, Gemini, etc.), one approach that's been working well is using a routing proxy that automatically picks the cheapest capable model per task. I built InferCut for this — it's a drop-in proxy (same OpenAI-compatible API, one line to switch) that routes requests to the most cost-effective model. Typical savings are 30-50% on API bills because not every task needs GPT-4o. For people hitting caps here and considering the API route, the key optimization is model tiering: simple tasks (file renames, formatting) on cheaper models, complex tasks (architecture, debugging) on premium models. Most people send everything to the same model and overpay. There's a detailed cost comparison table here if anyone wants to see per-model pricing across providers: https://gist.github.com/e6o/23db9719f8d9c173234ec7471e044a36 |






Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Is the limits for the Plus tier in the ChatGPT app the same as the limits in codex? (3000 Thinking/week)
All reactions