The Codex weekly allowance vanished in hours
On the same subscription tier, changing the reasoning tier can move consumption by an order of magnitude. Work out where it went before deciding to downshift, top up, or switch.
Four observations
How fast a weekly allowance can go
Reported repeatedly: on the same tier, high-reasoning work can exhaust a full week in a few hours.
Logged on a $200 tier
A developer recorded burning the $200 weekly allowance in a single day on long agent orchestration.
What extra credits felt like
One person topped up $20 and it was gone in under ten minutes; another added €100 and had single-digit euros left after an hour.
The most direct saving
Dropping work that does not need deep reasoning to a lower tier is the fix the community confirms most often.
Where the allowance actually goes
Token consumption for the same model differs sharply across reasoning tiers. The recurring pattern in public reports: running the highest tier on work that never needed deep thinking — bulk renames, boilerplate, test loops. Done on a lower tier or a cheaper model, the quality difference is often imperceptible while consumption differs by an order of magnitude.
About "when does the weekly allowance reset"
The community disagrees: some say it runs from your subscription date, others that most people reset on Thursday. There is no single public official statement covering every tier, so go by the time your own dashboard shows rather than by hearsay.
Timeline
Multiple developers publicly log high reasoning tiers exhausting a full week in hours.
First-person billing reports about extra credits cluster, from $20 to €100.
The phenomenon persists, though discussion volume has settled into the long tail.
Cut the burn rate first, then talk about switching
What is confirmed
Public discussion contains many first-person logs: high reasoning tiers exhausting a weekly allowance in hours, and extra credits consumed within ten minutes to an hour. These are user-reported billing experiences and are searchable.
Do not treat as fact
Claims that "the weekly allowance resets on Thursday for everyone" or that "the vendor quietly reduced allowances" have no official statement covering all tiers and no evidence at scale, so this page makes no such claim. The reset time shown in your own dashboard is the one that applies to you.
Two routes
Keep economising inside Codex
Downshift the reasoning tier, tighten scope, push simple work to cheaper models. No tool change, but the weekly ceiling is still the ceiling.
Switch model family when it runs out
One key, move to another family and keep working. Suits people already bouncing between two subscriptions. The cost is accepting different model habits.
Why topping up does not hold either
Extra credits are drawn down at the same unit price, so if your burn rate has not changed, any top-up burns at the same speed. One developer logged $20 gone in under ten minutes; another had single-digit euros left an hour after adding €100. Bring the burn rate down first, then decide whether to top up — doing it the other way round means topping up forever.
What QCode can and cannot do here
What it can do: when the Codex allowance is gone, use the same key to move to Claude, Gemini, GLM, Kimi, DeepSeek or Qwen and keep working, without buying a second subscription. Some people also run cheap models for execution and an expensive one to finish, pulling total consumption down. What it cannot do: we cannot change OpenAI’s weekly allowance mechanics or make your Codex subscription larger.
FAQ
Why is the same work eating the allowance faster this week?
Most often the reasoning tier changed, or the model widened the scope on its own. Start by checking whether the highest tier is being spent on work that never needed deep thinking.
Are extra credits worth it?
It depends on whether your burn rate came down. Credits draw at the same unit price, so an unchanged rate burns them at the same speed. Reduce the rate first, then top up.
When exactly does the weekly allowance reset?
Community reports disagree and there is no public official statement covering every tier. Use the time your own dashboard shows.
Does moving to QCode solve the weekly limit?
Not the OpenAI-side weekly limit itself. What it solves is "the allowance is gone but the work is not" — one key, switch family, keep writing code.
How is QCode billed differently?
By a daily limit rather than a weekly allowance, resetting at 00:00 Beijing time. If the day runs short you can self-serve a booster pack, which resets separately at 02:00 the next day. Predictable cost is the main characteristic.
Are cheaper models good enough?
It depends on the task. Some developers report no perceptible quality difference after moving execution work to a cheaper model; others hold that complex reasoning still needs the expensive one. The sensible pattern is layering: cheap model executes, expensive model finishes.
Sources
The phenomena and figures cited here come from publicly searchable developer discussion between 2026-07-30 and 2026-08-20. Note that earlier official quota-reset announcements are historical events and do not describe the current state; this page does not cite their engagement figures as evidence of present-day heat.
Allowance gone, work still due
One key across seven model families, billed by a daily limit with predictable cost.
Related reading
Codex quota and banked reset
How the reset mechanism works and what people get wrong.
The Codex 5-hour limit
How the short-cycle cap is calculated.
GPT-5.6 Sol ultra-fast tier
What this tier is for and what it costs.
Third-party quota mechanics described here follow each vendor’s official documentation and may change at any time. User experiences quoted are self-reported in public discussion and are not a promise about consumption rates on any tier.