Tell me about it. I’ve purchased additional hardware for the reset and now its just sitting there on dedicated server waiting for reset.
Is ChatGPT really becoming this stingy?
Previously, the usage limit would reset every 5 hours, with a weekly reset as well. Now it seems like there’s only a weekly reset. I honestly don’t care that much about not having a manual reset option—the real problem is that the quota only resets once a week.
Have you actually tried using it yourselves? The quota can be used up in less than a day, and once that happens, users have to wait until the following week before they can use it again.
Plus costs around $60 a month, yet the usage limits are this restrictive? Seriously?
Please compare your offering with other products on the market. Or at the very least, bring back the 5-hour quota reset.
If this continues, you’re going to lose a significant number of users. If you don’t believe it, just wait and see.
i’d say the opposite?
Do you understand there’s costs for OpenAI and they’re giving access to billions around the world? They’re trying to keep access available to all while keeping the servers up until they can acquire more compute/electricity.
You can choose to use the API which still has rate limits, but should give you a bit more stability for professional jobs. ChatGPT is more of a consumer product, imho.
Welcome to the community! Be sure to take a few minutes to check out our history here!
1 Like
I wonder if part of the recent sudden increase in Codex usage could be related to larger context usage, particularly in long-running sessions.
There are a few interesting facts that seem worth connecting.
According to OpenAI’s official GPT-5.6 Sol model documentation, the model supports a 1,050,000-token context window and up to 128K output tokens.
The current Codex model metadata for GPT-5.6 Sol shows:
context_window: 272000
max_context_window: 872000
So 272K remains the default, while Codex now supports opting into a substantially larger context window.
More importantly, OpenAI’s GPT-5.6 Sol documentation states that prompts with more than 272K input tokens are priced at 2x input and 1.5x output for the full request.
OpenAI’s Codex usage documentation also explains that larger codebases, long-running tasks, and extended sessions that require Codex to hold more context can use significantly more usage per message.
Tibo Sottiaux from the Codex team also recently explained how to enable the larger context window for GPT-5.6 Sol, and in a separate post noted that there had been a recent change to Codex’s context handling, while also emphasizing that the normal Codex context limit was tuned with performance and cost in mind.
That makes me wonder whether some of the unexpectedly high Codex quota consumption users are seeing could be related to substantially more context being retained or processed during long-running sessions — particularly for users using the extended context window, or if anything recently changed in how much context Codex retains between turns.
I am not claiming this is definitely the cause. The >272K multiplier refers to API pricing, and we do not know exactly how ChatGPT/Codex subscription quota accounting maps to API token pricing.
But it would be useful if the Codex team could clarify:
Has anything recently changed in the amount of context Codex retains or processes during long-running sessions, and does using the extended context window — particularly beyond ~272K tokens — materially increase the rate at which ChatGPT/Codex subscription usage limits are consumed?
If so, that could explain at least part of the sudden usage increase users are reporting.
Can you give us the link to where Tibo Sottiaux explains how to set larger context window in 5.6?
Because I’m unable to use more than default for months.
Also, the sudden drain of usage limit occurs on the default context window of about 250k tokens for me. So it’s not because of larger context windows, yet I’m still curious how to change it now so that it’s visible it changed.
ChatGPT 5.6 on very high reasoning says you can’t do that in Codex 5.6 at all. That it’s been disabled.
this one?
this might also be relevant…
i’ve been thinking of starting a thread for Codex tips and tricks… any interest from anyone?
It kind of sounds like you’re thinking we should be thankful it’s not worse.
i mean, honestly, it could be better or worse depending on how you look at it? 
take a step back and think about what they’re trying to do and how they’re trying to be fair to as many people as possible. not an easy task with so many bad actors out and about.
the normal devs like us end up paying for some taking advantage however they can, but i do see things improving relatively soon. we’re due another “breakthrough” soon, imho! 
but yea, is the glass half-empty or half-full currently when it comes to OpenAI?
growth pains have gotta be crazy for them to deal with internally and externally.
i’ve been thinking of starting a thread for Codex tips and tricks… any interest from anyone?
I spent $500 of my personal cash in the last 4 days just trying to keep my work project alive because I enjoy working with ChatGPT and doing things I only dreamed about before. That’s at the regular usage that in the weeks before was within the limits of my OpenAI subscription.
In one case, last week when Sol was affordable, my system did in 15 minutes what a top-tier sql developer said would take so long that it was impractical. True story. Probably saved the company $5k minimum had they funded that development, but the truth is that they wouldn’t have funded it at $5k.
For a business, it’s not a matter of brand loyalty or appreciation of “fairness”. If users can’t afford it, they will seek alternatives. At $1000 a week, hardware for an on-prem llm that will run GLM is looking like a reasonable investment, as insane as that sounds. haha…
Wow… Locked out of my account now…
{“error”:{“code”:502,“message”:“Bad gateway.”,“param”:null,“type”:“cf_bad_gateway”}}
Anyone else having this issue?