Skip to content

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

Open

Description

@ouriellilti-art

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.

Activity

  1. added
    bugSomething isn't working
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Sep 15, 2026
  2. pedrometer12 commented on Sep 16, 2026

    @pedrometer12

    I have experienced what appears to be the same or a closely related problem, with purchased credits being consumed at a rate that cannot be reconciled with the work performed or the usage analytics. I have filed a separate report with the details and evidence here: #45932
    I have also raised the disputed usage with OpenAI Support, but have not yet received an explanation or had the credits restored. There appears to be a similar earlier report at #36622 as well. I am currently unwilling to purchase further credits because I cannot safely reproduce the problem without risking losing more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reporting

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions