Quota drained instantly: 100 credits gone after 1 message, 5h limit reset to 0%

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #29604
• #29308
• #29895
• #28879
• #29587

Powered by Codex Action

We met the same issue. Moreover, we have two 200$ pro users. Both capacity are gone.

$200 plan also draining fast, fix the issue.

me too

Same issue on ChatGPT Plus.

Around 08:00 ICT (UTC+7) on 25 June 2026, my 5-hour Codex allowance went from over 90% remaining to 0% after one short prompt that produced one line of code.

I used my one available reset token. The allowance showed 100% immediately after reset, then dropped to 49% after one short prompt and later reached 0%.

This also consumed my reset opportunity.

I'm the same. After sending a message, my credit limit was used up. I purchased 200$ plan

Quota drains while idle: 100 credits consumed and 5h limit decreases even without running a task

no-active-thread-019efcfe-bb54-7190-a0c1-fd484390afec

Adding another data point: I'm hitting the same accounting over-consumption pattern described here, with hard evidence from the upstream error stream.

On 2026-06-25, one of my Pro accounts hit usage_limit_reached, then the 5h limit reset, and the SAME account reached usage_limit_reached again only ~41 minutes later. Across that 41-minute window, actual billed usage for the two active Pro accounts combined was only ~1.35M tokens (~1.05M input + ~6K output across 48 successful requests) — i.e. a small amount of real usage burned 100% of a freshly-reset 5h Pro limit.

For comparison, the same account earlier the same day consumed ~156M tokens inside a 5h rolling window before the limit triggered. So the same plan/account hit the same limit at 1.35M tokens (41 min) vs 156M tokens (5h) — a ~115x discrepancy that cannot be explained by real token consumption.

Relevant upstream error payload I captured:
status: 429
error: { "type": "usage_limit_reached", "message": "The usage limit has been reached", "plan_type": "pro", "resets_in_seconds": 15648, "eligible_promo": null }

Symptoms match exactly:

• 5h limit resets, one (small) burst of requests, limit drops to 0% immediately
• eligible_promo: null (no bonus-credit path)
• idle periods between bursts show no usage on my side, yet the limit is still fully consumed right after the reset

This strongly suggests a server-side quota accounting bug where consumption is massively over-reported after a reset, rather than proportional to actual token usage.

mee too

same, pro20x -->plus

And someone got pro5x --> pro 20x, make this really weird.

me too. 20x and 5x both get rate-limit.

yes,me too.

+++

<img width="2200" height="608" alt="Image" src="https://github.com/user-attachments/assets/819e5273-f2d6-4524-a571-2d52c6f2324f" />

<img width="2268" height="578" alt="Image" src="https://github.com/user-attachments/assets/d029efcf-9df9-4d7a-a4e6-47dacbca5c98" />

<img width="2268" height="608" alt="Image" src="https://github.com/user-attachments/assets/7f647332-c1d8-48e9-92e4-e02116ef270b" />

<img width="638" height="382" alt="Image" src="https://github.com/user-attachments/assets/76ded19c-29cd-4b6d-99c2-dd8308127cf0" /> who can help me？I only sent two "hello" messages today, but my credit limit is completely used up. Who will compensate me for the lost credit limit?

Me too

one message and quoto gone, why??

修好了吗？

I'm having the same issue on 5x pro plan, one message and 5h quota is gone.
Feedback id 019eff07-c4b9-7971-ad3a-60fe2478ea0c

Same here, I used up half of my weekly Pro Lite allowance in three minutes.

<img width="2281" height="580" alt="Image" src="https://github.com/user-attachments/assets/8440cb84-2a12-4d62-9e1a-564e33a72628" />

having the same issue unfortunately. two 20x accounts

Same here! please fix! I used up half of my weekly plus allowance in a minute.

It seems to have been fixed in Codex App 26.623.31443? I'm not quite sure though.

我的plus套餐一个上下文压缩就用了10%的额度！

Adding another Windows Desktop datapoint.

Environment:

• Codex Desktop: 26.623.3763.0
• Platform: Windows
• Account: GitHub/Codex user Norton-Jul

Observed on 2026-06-26: Codex usage/credits were consumed abnormally fast during ordinary interactive troubleshooting, far more than expected relative to the visible work in the thread. This was not an intentionally long autonomous run. The symptom looks consistent with the quota/credit accounting issues described in this thread and related reports.

Please investigate server-side usage accounting for affected accounts/sessions. I can provide timestamps, screenshots, and session details privately if needed.

I’m seeing the same issue as well.

I’m using ChatGPT Pro 5x , but recently the rate limits feel much stricter than before. Previously, even the 5-hour limit felt generous enough that it was difficult to fully use it up during normal work. Now, with a similar usage pattern, I can reach the weekly limit in around two days.

This feels like abnormal behavior rather than normal usage, and it may be related to the quota accounting / rate-limit issues reported here.

Could you please check whether this is expected behavior, or whether there is a regression affecting Pro 5x users?

I can provide a /feedback session ID if that would help with the investigation.

Feedback ID

019efeca-c472-73e3-b68e-9f670789213f

Adding an updated anonymized datapoint from Windows / Plus plan.

Date/timezone: 2026-06-27, Asia/Shanghai.

Observed behavior:

• 5-hour usage window started / reset around 11:26, with next reset shown as 16:26.
• I started using Codex around 11:30.
• After only 2 user prompts, the 5-hour usage remaining dropped to 78%, meaning 22% of the 5-hour quota was consumed within a few minutes.
• A local request/accounting tool (cc-switch) reported only about 355,515 real consumed tokens for that same period.
• The same tool showed 6 Codex session requests, roughly 264k input tokens, 5,083 output tokens, about 86k cache-hit tokens, and total estimated cost around $1.5164.

This looks disproportionate: 2 user prompts / ~355k real tokens should not appear to consume 22% of a 5-hour Codex usage window on Plus within several minutes.

Please investigate whether the 5-hour quota accounting is being over-debited, whether cache-hit tokens are counted incorrectly, or whether background/session requests are being charged against the interactive quota unexpectedly.

Same here!!

Is there any update on this, I can't use my plan, cuz it will get wasted in 1 prompt.

Try to logout and login, but before you can check at codex cli /status and see your plan become is Free (I think they have incident at this day and some problems with it), after re-login you see your real plan.

I hope its will be helpful

from codex cli update @0.142.4 / 0.142.5 tokens are depleting faster like Titanic ship is sinking in the sea due to bottom hole.

Summary

Codex usage accounting appears to drain the 5-hour limit abnormally fast on ChatGPT Plus, especially on July 2, 2026. Based on local Codex session logs on macOS, the primary 5-hour usage jumped from 70% to 100% in about 5 minutes 48 seconds during ordinary interactive use, and another local session shows 71% already consumed before the visible prompts in that session began.

This issue was written with a 5.5 Medium - 18% was drained in that. Before that, I had used a banked reset - the 100% 5hr from that drained within 26 minutes. This issue was not fixed. I was seriously considering upgrading from my Plus -> Pro, but if this is how its going to be then I'm not doing that.

This does not look like normal model usage. It looks like either:

incorrect usage accounting,
hidden/background usage attribution,
or a serious regression in per-turn weighting.
Environment
Platform: macOS
Plan: Plus
App: Codex Desktop / VS Code source
Observed models in affected sessions:
gpt-5.5 with medium effort
another July 2 investigation session on gpt-5.4 with medium effort also continued draining rapidly
Strongest evidence
Post-reset timeline on July 2, 2026
From local Codex usage log events after the reset:

2026-07-02 15:18:21 IST -> 1%
2026-07-02 15:18:30 IST -> 2%
2026-07-02 15:18:46 IST -> 3%
2026-07-02 15:19:21 IST -> 6%
2026-07-02 15:19:41 IST -> 7%
2026-07-02 15:20:00 IST -> 9%
Then later in the same local session history:

2026-07-02 15:40:11 IST -> 70%
So the local logs show a post-reset climb from 1% to 9% within about 1 minute 39 seconds, followed by a jump to 70% within about 21 minutes 50 seconds. I am not attaching raw session files here because they contain prompts, outputs, and local workspace details. I can provide sanitized token_count / rate_limits lines only if needed.

Session 019f1ee9-693d-7251-bd45-953c7de51d84
Feedback ID: 019f1ee9-693d-7251-bd45-953c7de51d84

This session is explicitly recorded as gpt-5.5 with medium effort.

Primary 5-hour usage timeline:

2026-07-01 23:51:00 IST -> 5%
2026-07-01 23:51:04 IST -> 7%
2026-07-01 23:52:49 IST -> 15%
2026-07-01 23:53:44 IST -> 20%
2026-07-02 15:18:21 IST -> 1%
2026-07-02 15:18:30 IST -> 2%
2026-07-02 15:18:46 IST -> 3%
2026-07-02 15:19:21 IST -> 6%
2026-07-02 15:19:41 IST -> 7%
2026-07-02 15:20:00 IST -> 9%
2026-07-02 15:40:11 IST -> 70%
2026-07-02 15:40:22 IST -> 72%
2026-07-02 15:42:05 IST -> 77%
2026-07-02 15:42:39 IST -> 80%
2026-07-02 15:43:13 IST -> 84%
2026-07-02 15:43:56 IST -> 87%
2026-07-02 15:44:58 IST -> 95%
2026-07-02 15:45:37 IST -> 98%
2026-07-02 15:45:59 IST -> 100%
That is a rise from 70% to 100% in about 5 minutes 48 seconds.

Session 019f224e-b04a-7ee2-a2ab-b61b66f3c944
Feedback ID:
019f224e-b04a-7ee2-a2ab-b61b66f3c944
This session shows:

2026-07-02 15:42:07 IST -> 77%
2026-07-02 15:43:16 IST -> 85%
2026-07-02 15:43:25 IST -> 86%
2026-07-02 15:43:33 IST -> 87%
Important detail: another local session file showed the early post-reset 1%-9% steps above, but this session history is where the later 70%-100% drain is clearly visible.

Session 019f17cd-bde4-7802-8e91-07528398fb02
Feedback id: 019f17cd-bde4-7802-8e91-07528398fb02

This earlier session shows a much more gradual pattern at the beginning:

2026-06-30 14:46:27 IST -> 3%
2026-06-30 14:46:33 IST -> 4%
2026-06-30 14:46:46 IST -> 5%
2026-06-30 14:47:06 IST -> 6%
2026-06-30 14:47:50 IST -> 7%
2026-06-30 14:48:16 IST -> 8%
2026-06-30 14:48:31 IST -> 9%
2026-06-30 14:48:36 IST -> 10%
2026-06-30 14:49:13 IST -> 11%
2026-06-30 14:49:19 IST -> 12%
2026-06-30 14:49:33 IST -> 13%
This makes the July 2 behavior stand out as abnormal.

Why this looks broken
A local gpt-5.5 session rose from 70% to 100% in under 6 minutes.
Another July 2 local session already started with most of the 5-hour budget gone, with no local session artifact from 15:25 IST to 15:40 IST explaining that jump.
The earlier June 30 session shows a much more incremental consumption pattern.
OpenAI publicly said a Codex usage-drain fix had been deployed on June 30, 2026, but this July 2 behavior still appears broken.
Ask
Can you investigate whether usage accounting is overcharging or attributing hidden/background work to the 5-hour limit?
Can you confirm whether per-turn weighting changed for Plus users around July 1-2, 2026?
If useful, I can provide the exact local JSONL session files and the token_count / rate_limits events from those files.

Nice breakdown, @gititya. I guess doing /feedback in each of the mentioned session-chat will give support more data than those files.