Pro Lite / Pro 5x: weekly quota depleted ~93% in one day after automatic reset despite comparable token volume

What subscription do you have?

ChatGPT Pro Lite / Pro 5x.

What platform / surface are you using?

ChatGPT / Codex Work desktop on Windows.

What issue are you seeing?

My weekly Codex/Work allowance was automatically reset twice over the weekend, and after the second reset the quota depleted dramatically faster than the previous day despite a very similar amount of raw token activity.

The main anomaly is:

• Aug 30: Analytics shows 344.8M raw tokens. I used roughly 30 percentage points of the weekly allowance during the day.
• Aug 31: Analytics shows 331.6M raw tokens, slightly less than Aug 30. After an automatic reset to 100% that morning, the weekly allowance fell to 7% remaining by the evening, i.e. roughly 93 percentage points consumed.

I understand that raw token count is not expected to map 1:1 to quota because cached input, uncached input, output, reasoning effort, model choice, subagents, etc. may be weighted differently. The bug report is therefore not claiming that 331.6M and 344.8M raw tokens must cost exactly the same.

The concern is that a comparable workflow and comparable raw-token volume produced roughly 3x the observed weekly quota depletion immediately after the automatic reset, with no user-visible accounting that explains the discontinuity.

Timeline (Europe/Stockholm)

• Sat Aug 29: approximately 30% weekly allowance remaining. The normal reset was scheduled for Monday.
• Sun Aug 30: allowance unexpectedly returned to 100% without me manually redeeming a reset. The next reset date moved to Sep 6.
• Sun Aug 30 evening: approximately 70% remained after the day's work. Analytics later showed 344.8M raw tokens for Aug 30.
• Mon Aug 31 morning: allowance was again back at 100% without manual redemption. The next reset date moved again, now to Sep 7.
• Mon Aug 31 evening: only 7% remained. The UI showed the next reset as Sep 7, 2026 13:21. Analytics showed 331.6M raw tokens for Aug 31.

For additional context, Analytics shows 66.6M raw tokens on Aug 29.

Secondary reset problem

The automatic resets also replaced the allowance I had deliberately saved before the normal reset date.

For example, if ~30% remained and I was due to receive a normal fresh weekly allowance shortly afterwards, an automatic reset to 100% followed by moving the next reset date a week forward effectively removed the value of the remaining ~30%. Previously, banked resets allowed the user to choose when to redeem them.

I am not assuming this has the same root cause as the abnormal depletion, but it is relevant to the timeline because both quota discontinuities happened immediately around automatic resets.

Expected behavior

• Comparable workloads on the same account should have broadly comparable effective quota consumption unless there is a disclosed model/runtime/metering change.
• If consumption changes sharply, users should be able to audit why.
• An automatic reset should not make already-earned/saved remaining allowance silently disappear without clearly communicating that effect.
• The UI should expose enough per-task accounting to reconcile quota deductions with actual work performed.

Requested investigation

Please correlate the server-side usage ledger for this account around Aug 30–31, 2026 (Europe/Stockholm) and check:

1. cached input / uncached input / output / reasoning token weighting;
2. model and reasoning-effort changes between the two days;
3. Fast/Ultra/subagent/delegated/background activity charged to the same bucket;
4. retries, compaction/context replay, polling/wait loops, or other hidden usage amplification;
5. delayed/backfilled usage or usage attributed across the automatic-reset boundary;
6. duplicate accounting;
7. the exact timestamps and reason for the automatic resets on Aug 30 and Aug 31;
8. whether quota from before either reset was carried forward, discarded, or otherwise reconciled.

I have screenshots of the Analytics values (344.8M on Aug 30, 331.6M on Aug 31) and the usage-limit UI showing 7% remaining / reset Sep 7 at 13:21, and can provide them if maintainers need them.

Related issues

• #41220 — abnormal Codex usage/quota depletion and usage-accounting inconsistencies tracker
• #41969 — recent Pro Lite / Pro 5x report of sudden weekly quota depletion after a stable baseline

No repository file or test is identified; start by reading related issues #41220 and #41969, then correlate the server-side usage ledger with the Aug 30–31 timeline. Check the listed token weighting, reset-boundary, hidden-usage, and duplicate-accounting possibilities; done means explaining the quota discrepancy and automatic-reset treatment or documenting the confirmed cause.