Suspected Codex usage metering/accounting anomaly: ~3 weekly allowances consumed in one day + rapid paid-credit depletion

What subscription do you have?

ChatGPT paid plan with Codex usage and purchased additional Codex credits.

What issue are you seeing?

I am reporting a suspected Codex usage-metering/accounting anomaly affecting both included weekly usage and purchased credits.

On September 14, 2026, my account consumed approximately three complete weekly Codex allowances in a single day: the normal weekly allowance plus two resets. This is highly abnormal compared with the previous week, during which substantially heavier coding activity fit within a single weekly allowance.

On September 15, 2026, I purchased $80 of additional Codex credits. Those credits are now being consumed at an unexpectedly high rate. At the same time, the Codex & Work analytics page shows a very large spike in Personal Usage that I cannot reconcile with my actual activity.

The key point is that the change is not explained by a simple increase in coding intensity. The immediately preceding week involved more coding work overall, yet consumed far less weekly allowance.

Expected behavior

Usage consumption should remain reasonably consistent for comparable workloads and should correspond to actual model/tool activity.

If usage is being reconciled later, retroactively attributed, duplicated, or affected by a metering bug, the account should not lose included usage or paid credits incorrectly.

Requested investigation

Please investigate the server-side Codex usage ledger for September 14–15, 2026, including, where available:

• usage attributable to each task/session;
• input tokens;
• cached input;
• output/reasoning tokens;
• model used;
• subagent usage;
• retries and tool loops;
• delayed or reconciled usage;
• any duplicate or retroactively attributed usage;
• the mapping between the analytics "Personal Usage" spike and actual Codex sessions.

Please also check whether a recent change in quota weighting, cache accounting, subagent accounting, or reconciliation logic could explain a several-fold increase in usage consumption for similar work.

Impact

• Approximately three weekly allowances were consumed in one day.
• Two resets were effectively burned immediately after the normal allowance.
• $80 of purchased credits are depleting unusually quickly.
• The analytics dashboard shows an unexplained Personal Usage spike on September 15.
• This currently makes it risky to continue using Codex for normal development work or to purchase additional credits.

Additional information

I have a screenshot of the Codex & Work analytics page showing the abnormal spike and can provide additional timestamps/session details if maintainers indicate what diagnostics are most useful.

I am also contacting OpenAI Support separately because account-level restoration/refund of incorrectly deducted usage or credits requires a private support channel.

This appears related in symptom class to other recent reports of unusually rapid quota depletion or inconsistent quota state, but this report documents an independent, recent reproduction involving both weekly allowance and purchased credits.

The report does not name a repository file, test, or code entry point; it requests server-side ledger and analytics investigation for September 14–15, 2026. Start by determining whether usage accounting and Personal Usage data are implemented in this repository or handled externally. Done would require reconciling sessions, credits, and quota consumption and identifying any duplicate or retroactive charges.