GPT-5.6 Plus weekly usage suddenly drained from ~99% to 0% within hours — possible usage accounting regression

What version of the Codex App are you using (From “About Codex” dialog)?

26.818.41509

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

My ChatGPT Plus Codex weekly usage appears to have been depleted abnormally fast on August 21, 2026.

My weekly allowance had recently reset. On the morning of Aug 21, the Usage Dashboard showed approximately 99% remaining. Within only a few hours, it suddenly reached 0% remaining and Codex became blocked.

At approximately 14:41 GMT+7, requests began returning:

HTTP 429 - usage_limit_reached
plan_type: plus

The visible Usage Dashboard currently exposes only the weekly limit. The previous 5-hour meter is no longer shown on my account since the recent GPT-5.6 usage changes.

I was using a local Hermes Agent connected through OpenAI/ChatGPT OAuth (openai-codex), not an API key. The workload that morning consisted mainly of routine agent tasks, scheduled briefings, Telegram integration testing, and operational-reminder setup.

I audited the complete local Hermes agent log for the relevant period. Before the limit was reached it recorded:

• 107 successful Codex model calls
• 101 GPT-5.6 Luna calls
• 6 GPT-5.6 Sol calls
• approximately 9.39M gross input tokens
• approximately 8.35M cached input tokens (~88.9%)
• approximately 1.05M uncached input tokens
• approximately 84K output tokens

There was no large successful Hermes workload between approximately 13:30 and 14:41 GMT+7. At 14:41 Codex immediately began returning usage_limit_reached.

However, Codex Desktop Profile analytics later reported 81.7M tokens for Aug 21.

This creates two concerns:

1. The server-side Profile total (81.7M) is much larger than the successful model activity I can reconcile from the Hermes local log (~9.39M gross tokens).
2. Even if the full 81.7M Profile total is correct, exhausting nearly the entire weekly allowance is inconsistent with historical usage on the same account.

For comparison, my Codex Profile shows:

• Aug 19: ~59.2M tokens, which I observed consuming only approximately 10-12% of my available usage.
• Aug 12: ~96.7M tokens during an intentionally very heavy usage day, which consumed roughly 60%+ rather than the entire allowance.
• Aug 21: 81.7M tokens, yet the weekly allowance went from approximately 99% remaining to 0%.

I understand that raw token counts do not map 1:1 to rate-limit consumption because models, cached input, reasoning and weighting differ. However, the magnitude and suddenness of this change appear inconsistent with the historical behavior of the same Plus account.

Please investigate whether this is caused by incorrect usage accounting, duplicated OAuth attribution, delayed/background usage attribution, or a regression in GPT-5.6 weekly rate-limit weighting.

What steps can reproduce the bug?

This is not reliably reproducible on demand because the suspected problem is server-side usage accounting. The observed sequence was:

1. Start with a recently reset ChatGPT Plus weekly Codex allowance.
2. Confirm that the Usage Dashboard shows approximately 99% remaining.
3. Use Codex through a ChatGPT/OAuth-connected local agent (Hermes Agent) with GPT-5.6 Luna and GPT-5.6 Sol.
4. Perform normal/light-to-moderate agent tasks, including scheduled briefings, file reads, Telegram testing and operational-reminder setup.
5. Observe normal usage initially; one morning briefing appeared to reduce the visible weekly allowance by only around 1%.
6. Continue normal usage for several hours.
7. At approximately 14:41 GMT+7, observe Codex immediately return HTTP 429 usage_limit_reached.
8. Open the Usage Dashboard and observe 0% remaining even though it had been approximately 99% earlier that day.
9. Later inspect Codex Desktop Profile analytics and observe 81.7M tokens attributed to Aug 21.
10. Compare this with local OAuth-agent logs, which show only 107 successful Codex calls and approximately 9.39M gross input tokens during the investigated period.

Relevant investigation window:
August 21, 2026
approximately 08:00-14:45 GMT+7
approximately 01:00-07:45 UTC.

I can provide sanitized local logs containing timestamps, model names, cached/uncached token counts and the final HTTP 429 response.

What is the expected behavior?

Weekly usage should decrease consistently according to the actual weighted Codex workload.

A ChatGPT Plus weekly allowance that is approximately 99% available should not suddenly become 0% within a few hours unless the account actually performed enough weighted inference to consume the full allowance.

OAuth-connected agents should not have requests duplicated, incorrectly attributed or charged multiple times.

If background tasks, subagents, automatic reviews or another Codex/Work surface consumed the allowance, the user should have an auditable usage breakdown showing which surface, model and activity caused the consumption.

The Codex Profile token analytics and the rate-limit meter should also be sufficiently consistent and transparent that a user can determine why an allowance was exhausted.

If the weekly allowance or per-model weighting changed with GPT-5.6, that change should be reflected clearly in the product and documentation rather than appearing as a sudden unexplained depletion.

Additional information

I searched existing openai/codex issues before filing this report.

Potentially related reports include:

• #33685 — "Weekly limit is draining like the old 5-hour limit"
• #30918 — Plus usage limits draining abnormally fast
• #28879 — rate-limit cost per token increased dramatically
• #35463 — weekly quota drained abnormally with subagent activity
• #32503 — GPT-5.6 tool-call behavior multiplying model turns and quota usage

My case appears related but is not identical.

Important differences in this report:

• ChatGPT Plus
• GPT-5.6 Luna was used for most of the successful calls
• The visible 5-hour meter has disappeared; only the weekly allowance is shown
• Weekly usage changed from approximately 99% remaining to 0% within a few hours
• Codex Profile eventually attributed 81.7M tokens to Aug 21
• The investigated Hermes OAuth client log accounts for only ~9.39M gross input tokens from successful calls during the relevant period
• Approximately 88.9% of those locally recorded input tokens were cached
• No large successful Hermes workload is visible between approximately 13:30 and the first usage_limit_reached response at 14:41 GMT+7
• Historical usage on the same account was substantially more predictable: ~59.2M tokens on Aug 19 consumed only around 10-12% by my observation, while a ~96.7M-token intentionally heavy day on Aug 12 still did not instantly consume the entire allowance.

I also contacted OpenAI Support. The issue was escalated to a specialist, but the first-line support view could only confirm that the weekly allowance was fully consumed and could not provide a per-request usage breakdown.

Evidence available:

• Screenshot of 0% weekly usage / reset date
• Screenshot of Codex Profile showing 81.7M tokens on Aug 21
• Historical Profile token activity
• Sanitized Hermes agent log with model calls, token counts, cache ratios and timestamps
• HTTP 429 usage_limit_reached log entries

I can provide additional sanitized diagnostic data if requested.

No repository file, test, or entry point is identified; begin by locating the server-side usage accounting and rate-limit handling components. Compare the reported Hermes logs, Profile analytics, and weekly meter for the August 21 window, and consider the investigation complete when the discrepancy is explained or a confirmed accounting regression is isolated.