Codex credits consumed ~39,000 overnight with zero tasks — recurring bug, cap not enforced (GitHub #38294)

Codex
1

Has anyone else experienced this? Codex credits have been abnormally consumed twice on my account, and I can’t find a clear explanation.

What happened:

Incident 1 (last Thursday)

  • Credit cap: 5,000
  • Was working in the afternoon → suddenly hit “limit exceeded” with no prior warning
  • Usage showed 38,140 credits consumed — 7x the cap

Incident 2 (last night)

  • Credit cap: 10,000 (raised by org after Incident 1)
  • Last task at 01:02 KST, Codex last responded at 01:03 KST
  • Went to sleep — zero tasks after 01:03
  • Woke up at 10:14 to: “You have reached the usage limit”
  • 39,078 credits consumed in ~9 hours while I was asleep

What makes this clearly a bug:

  • Both incidents produced nearly identical totals (~38,000–39,000) despite different caps (5,000 vs 10,000)
  • Cap was exceeded by 7x and 4x respectively — not being enforced at all
  • Incident 2 happened entirely while I was asleep with zero tasks
  • No low-credit warning before cutoff in either case
  • /usage is blocked due to “no credits remaining” — can’t even self-diagnose

This also appears to be affecting others in my organization. A company-wide notice has been issued internally regarding abnormal Codex credit consumption.

Already filed with OpenAI Support (case on file) and GitHub issue #38294.

Anyone else seeing this pattern?

2

I’m also experiencing a very similar Codex credit consumption/quota issue on my account.

My account is on the $200/month 20× plan, and after the reset on August 11, 2026, the weekly quota appears to be incorrect.

Normally, the expected weekly allowance for my plan should be around 55,000 credits, but after the reset my usage data showed:

"credits": 11951.706005000002

This looks much closer to a single 5-hour limit allocation, rather than the full weekly quota.

The issue has now appeared after two separate quota resets, so I suspect this may be related to the reset process or account quota assignment rather than normal usage behavior.

I can also see the rapid consumption reflected under API pricing:

Weekly 6d20h35m 80%

59.06M
$66.50
08/20 11:36

The weekly limit appears to be behaving like the quota of a lower tier (possibly around the $300 API pricing equivalent), rather than the expected allocation for a 20× subscription.

Could the team please investigate:

  • Whether the reset process is assigning the wrong weekly credit cap.

  • Whether my account is correctly mapped to the $200/month 20× Codex plan.

  • Whether the weekly quota after reset is incorrectly inherited from another limit tier.

  • Whether this issue is related to the same backend accounting/cap enforcement bug reported here.

This has happened after multiple resets, so it would be helpful to check the account-level quota configuration and reset history.

Thanks.

3

Update: the issue appears to be getting worse after another Codex reset.

After the latest reset, my $200/month 20× Codex plan received an even lower weekly allocation.

Previous reset:

credits: 11951.706005000002

Latest reset:

credits: 8503.59619

This is significantly below the expected weekly allowance (~55,000 credits for this plan). The current allocation looks more like a short-term usage window quota rather than a full weekly entitlement.

The important point is that this does not look like normal high usage or credits being consumed too quickly. The problem appears to be that the weekly quota assigned after reset is incorrect.

The issue has now reproduced across multiple reset cycles:

  • Reset #1 → ~11,951 credits assigned

  • Reset #2 → ~8,503 credits assigned

Both times the account was unable to receive the expected 20× weekly allowance.

The UI also confirms the account is fully exhausted:

  • “You’re out of Codex and Work usage for now”

  • Weekly usage limit: 0% remaining

  • Credits remaining: 0

Could the Codex team please investigate whether:

  • The reset process is assigning the wrong quota bucket.

  • The account entitlement mapping for the $200/month 20× plan is incorrect.

  • The weekly limit is being inherited from another tier or temporary usage window.

  • This is related to the same quota/cap enforcement issues reported in this thread.

This looks like an account provisioning/reset issue rather than a normal usage consumption issue.

Thanks.