Codex quota consumption has a serious bug

Open 💬 10 comments Opened Jun 25, 2026 by cNa2017
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

code-app Latest,codex-cl iLatest

What subscription do you have?

pro 20x

What platform is your computer?

macOs、Ubuntu

What issue are you seeing?

<img width="1274" height="817" alt="Image" src="https://github.com/user-attachments/assets/296c24a8-4aea-4e11-9088-607505bb2561" />

codex 从2026-06-25 开始 额度消耗比以往块了1000倍,Pro 20x 订阅套餐,一次普通review(单线程)就能在5分钟内把 5小时额度全部使用完,周额度消耗了 16%。简直离谱了。

What steps can reproduce the bug?

Feedback ID: 019efc95-f5cb-77e0-be7e-7769dd718753

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

10 Comments

github-actions[bot] contributor · 26 days ago

English translation:

What version of the Codex App are you using (From “About Codex” dialog)?

code-app Latest, codex-cl iLatest

What subscription do you have?

pro 20x

What platform is your computer?

macOs, Ubuntu

What issue are you seeing?

<img width="1274" height="817" alt="Image" src="https://github.com/user-attachments/assets/296c24a8-4aea-4e11-9088-607505bb2561" />

Starting from 2026-06-25, Codex quota consumption has become 1000 times faster than before. With the Pro 20x subscription plan, a single normal review (single-threaded) can use up the entire 5-hour quota within 5 minutes, and 16% of the weekly quota was consumed. This is simply outrageous.

What steps can reproduce the bug?

Feedback ID: 019efc95-f5cb-77e0-be7e-7769dd718753

What is the expected behavior?

_No response_

Additional information

_No response_

<!-- codex-issue-translator -->

github-actions[bot] contributor · 26 days ago

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

  • #29955
  • #29604
  • #28498
  • #29895
  • #28879

Powered by Codex Action

vincent19951222 · 26 days ago

same issue,5h usage was consumed within 5 mins

rurico · 25 days ago

Same here. As a Plus user, I experienced a ridiculous spike in quota consumption today.

  • Context setting: 5.4 Low
  • Input prompt: Just a single short instruction: return ok
  • Impact: This single action burned through 33% of my 5-hour tokens and 5% of my weekly tokens.

The accounting logic is definitely broken for Plus accounts. Looking forward to a fix and a quota restoration.

(Attached my screenshot below)

<img width="842" height="378" alt="Image" src="https://github.com/user-attachments/assets/383d1b30-ec8f-4cc9-8adb-0201315e26e4" />

cop588 · 25 days ago

I’m seeing the same issue today.

On 2026-06-25, two separate ChatGPT Plus accounts started draining Codex quota abnormally right after the quota reset. In both cases, a single normal Codex task exhausted the available quota within about 5 minutes.

This does not look like normal high usage or a large-context task. The key detail is that the abnormal drain started immediately after the reset on both Plus accounts.

This seems like a quota reset / rate-limit accounting bug rather than a normal model usage increase. It directly consumes paid Codex entitlement, so please treat it as a paid quota accounting issue and investigate whether affected users can have incorrectly consumed quota restored.

liangjiawei1992 · 25 days ago

I've encountered the same issue. I've been waiting for a day, but I haven't received a reply yet

lain-creator · 25 days ago

The same problem

jkooooo99 · 24 days ago

same problem here!!!!!!!!

manfredlift · 24 days ago

same here

simfor99 · 18 days ago

I am seeing a very similar quota/accounting issue on a ChatGPT Pro 20x subscription.

Observed on 2026-07-02, Europe/Berlin:

  • Codex CLI: v0.142.5
  • Model: gpt-5.5, reasoning high, summaries auto
  • Billing / ChatGPT plan page: ChatGPT Pro 20x
  • Codex /status account label: Pro Lite
  • /status showed 5h limit: 77% left, weekly limit: 43% left
  • GPT-5.3-Codex-Spark limits: 100% left
  • Immediately after that, a normal prompt was rejected with: You've hit your usage limit ... try again at 11:28 AM.

The machine had been powered off overnight, and I had only worked for roughly ~2 hours in the morning before hitting the 5-hour window limit. This does not look like normal Pro 20x consumption. It looks like either:

  1. the wrong quota bucket / entitlement is being applied (Pro Lite vs ChatGPT Pro 20x),
  2. the 5h usage accounting is draining too quickly, or
  3. the usage display and enforcement are reading different backend state.

Happy to provide screenshot evidence through a private support channel, since it contains account-identifying details.