Abnormal Codex usage accounting exhausted remaining weekly allowance instantly

What issue are you seeing?

I am seeing what appears to be abnormal Codex usage accounting today (August 26, 2026).

Immediately before the incident, my Codex usage dashboard showed approximately 78% remaining. Shortly afterward, the remaining allowance suddenly dropped to 0%. When I inspect today's usage, it shows an abnormally large amount of usage that appears to have consumed all of the remaining allowance at once.

This does not match my observed Codex activity and is substantially different from my normal usage pattern.

Request

Could the Codex team please investigate the server-side usage/accounting records for my account and determine:

1. What specific Codex sessions/tasks generated the unusually large usage today.
2. Whether token/compute usage was counted correctly.
3. Whether a stuck/background session, subagent, retry loop, duplicated accounting, or other usage-accounting issue caused the sudden consumption.
4. Why the remaining allowance changed from approximately 78% to 0% in a very short period.
5. Whether incorrectly counted usage can be corrected/restored after investigation.

There are other open reports in this repository describing unusually high usage or quota changes without corresponding activity, so this may be related to an existing rate-limit/usage-accounting issue.

Please let me know what additional identifiers, timestamps, screenshots, session/thread IDs, or diagnostic information are needed to trace the affected usage.

No repository file, test, or entry point is named; begin by locating the Codex usage and quota-accounting components, then review available server-side logs and account identifiers. Done means identifying the sessions or accounting path responsible, confirming whether usage was counted correctly, and documenting whether restoration is possible.