Seems like I made a silly mistake (fall into trap?) and bought 6 seats of 1-year business plan, just was impressed with Codex capabilities.
After 5h limit change I can do approx 10x-15x less of what I was doing just a week ago.
Made bunch of skills, thought I could automate my business flaw a bit and kaboom!
Today I hit 5h limit within half task which literally feels like ten or more times less of what I was doing. I could understand cutting limit twice or moreâŚbut 10 times??
Is this a bug or the company âstrategyâ? I think Iâm not alone hereâŚ
Itâs very much real. Our multi-seat account hit 5 hour limits within minutes and our credit pool which used to last about a month, gone in 2 days. I almost made the mistake of switching the business over to yearly subscription but decided to hold off a few days before pulling the trigger. Itâs extremely unfortunate and I hope itâs an honest mistake, because otherwise this would be one very dishonest business move on their part. This is very painful now that weâve wrapped so much of our automation and development around it.
Yeah and my business partner was like âdude buy monthly donât go for a yearââŚI was like âcome on what can go wrong, weâre going to use it anyways and I kinda want to support amazing team of OpenAI for the great toolââŚLOL
I started a not-terribly-ambitious project back in February, creating an in-house tool that improved email filing in Clio.
At first, everything worked great. I was building my project one slice at a time in my free time after work. I was blissfully unaware that usage limits even existed.
Then, around mid-March, I started hitting my weekly usage limit after 3-4 days of use. Same usage pattern: maybe 10-12 prompts on a heavy day, all written by ChatGPT, about 2/3 of which were just small, corrective passes to fix bugs. I am using Codex through its VS Code integration, which is supposed to burn less usage than the web interface, and have been using 5.4-Mini where appropriate to minimize usage even further.
On April 3, after my weekly usage quota had reset, I tried to get started again. This time, I was able to run one feature-hardening pass (not even creating a new feature, just fixing one that already exists) and two tightly-focused passes to fix bugs after the hardening pass. Those three small, focused prompts used up my entire 5-hour quota and 12% of my weekly quota.
This is completely unacceptable. I am trying to build something in my spare time on a Business-tier subscription and cannot run more than three small passes without hitting usage limits. I canât imagine trying to use Codex for anything more ambitious or full-time. At this rate, it will take me months to complete a project that is already substantially finished.
If your goal was to push everyone away from using Codex for anything, well, congratulations, I guess. Mission accomplished. Youâve created a hammer that can only be swung three times per day. Great job.
Seeing the same on my side â and honestly, this isnât workable.
A few small, focused passes burning through quota breaks any real development flow, even for simple tasks. Thatâs especially hard to justify on a paid tier.
I appreciate the promo period â it was genuinely useful.
Rolling back to normal limits is fair.
But this feels like an overcorrection. At this level, Codex becomes hard to rely on for consistent work.
Also worth noting: decisions like this create an opening for alternatives (GLM-5, Kimi K2, etc.) to offer more predictable conditions.
Yeah, i have also opened another topic regarding this matter, thread: âcodex-limits-finally-good-after-april-1st-resetâ floating in newest topics.
Its going nuts now. I am running Business accounts with multiple user for multiple devs.
Yesterday and today the workflow is basically this:
Dev logins into CODEX on IDE
Sends 3 tasks
Dev must logout, ask me for new login approval
Dev then does again 3 tasks, logs out
To infinity this loopâŚ
Weekly limits seems like fair and ok IMO. But 5H its going absolute nuts. Each task eats 20-30% of 5H range.
You can actually test it by just writing something simple, just talking with it and you gonna see that it will suck 10% to answer
Also i have noticed the quality of the work went down from codex
But yes, its is becoming absolutely unusable at this point.
Im running GPT 5.4, Medium, Full access, Locally - no MCP connectors, nothing just purely controlled by core agent. So my tasks are super efficient and accurate.
We tired working on GPT5.3-codex, little better situation - you can produce just a little more but still same - 5H gets wiped off super fast.
The only choice is API or new Codex account credits at this point but budget must be super high, you can easily spend 50-100$ a day.
Suggestion: give admins the option to make Codex usage a pooled resource. I work for a law firm with 10 ChatGPT users on a business-tier license. Nobody else in our workspace is using Codex at all. If our account admin could pool our Codex quotas, I wouldnât constantly hit work stoppages due to usage limits.
While pooling quotas wouldnât fix the problem for everyone, it would at least fix it for similarly-situated users who burn through their quota while other users in the same workspace never even touch theirs.
Honestly that feels like an insane take. The problem is most certainly the way OpenAI decided to deal with things, like these credits and limits, but Codex, since 5.3, is absolutely blasting away any other LLM Iâve ever seen when it comes to coding.
I hadnât noticed it yet, possibly because I hadnât closed my Codex in days⌠But now I have hit the new limits and itâs exactly as others are saying. I just gave it 3 minor prompts, thinking nothing of it as I rarely hit my 5H limit anyway⌠And then it happened⌠3 minor prompts, and; You have hit your limit!.
Since the latest changes, introduced in Apr â26, our ChatGPT Business seats have become nearly useless. A simple prompt with a well defined unit of work now consumes nearly the entire 5hr limit and the weekly limit is proportionally equally evaporated. As a business which has been using Codex since its inception, this is the first time weâve had any such issues and hence Iâve resorted to this post.
I primarily noticed when our credits pool, which we would generally only hit lightly during extremely heavy sprints, has now burned through 10k+ credits in just 1 to 2 days, on top of three standard ChatGPT Business seats.
There has been a noticeable change also in the output structure of at least the GPT 5.4 model in the past few days. Not sure if related to the consumption change, but there appears to be much more feedback from the model and I believe much more context utilization for setup before action. Iâm seeing in some instances nearly 40% of the 258k context used compared to around 25% for the same codebase and similar tasks.
To keep this succinct - this service has become unaffordable and unsustainable for us overnight.
Weâve had no other significant issues and generally experience good performance from the models working in highly technical projects, spanning many scientific/engineering domains.
At best with the recent changes, i could get a max of 3 prompts in 5 hour period. That translates to 5 hour window finished in less than 20 minutes total time. And includes me making coffee in the kitchen and coming back. So most of the time spent was me entering a prompt and to eventually come back with coffee.
And the quality of responses for the lousy 3 prompts was also lousy. ChapGPT also didnât finish the task in any capacity. It delivered broken code. Not just logically wrong, but broken too.
I signed up for Claude 5x. Maybe I will upgrade to the 20x. Itâs been working great.
I think weâre talking about slightly different things.
First of all â Iâm genuinely grateful for the promo period.
The x2 limits were generous and gave many of us a real chance to explore Codex properly.
Returning from a temporary promo back to normal limits is completely fair and expected.
The issue is not the rollback itself.
The issue is the scale of what comes next.
Announcing an effective 5â8x reduction from the level people were actively using â shortly after encouraging deeper adoption â creates a serious expectation gap.
From a product perspective:
expectations were raised
workflows adapted
then capacity drops far below that level
Thatâs where the problem is â consistency and predictability.
For context: Iâm an indie developer.
My current project is for children with developmental challenges. Itâs completely free and generates no revenue.
So this is not âcomplaining about losing free compute.â
Itâs simply stating a practical constraint.
Not everyone is building for immediate monetization â and those use cases still depend on stable assumptions.
Also, suggesting multiple accounts is not a real solution â itâs against policy and not sustainable.
To be clear:
I appreciate the promo â genuinely
returning to normal limits is reasonable
but cutting 5â8x in one step is a clear marketing and user-experience miss
Even a 2x reduction would be understandable.
This scale of change is not.
