Codex weekly quota almost fully consumed while usage dashboard shows only ~59k tokens used #35186

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

26.721.31836

What subscription do you have?

ChatGPT Plus

What platform is your computer?

No response

What issue are you seeing?

Description

My Codex weekly quota was almost completely consumed today, but the Codex usage dashboard shows only around 59k tokens used.

The displayed token usage and the actual quota consumption appear to be inconsistent.

Environment

• Plan: ChatGPT Plus
• Platform: macOS app + Web ChatGPT
• Codex version: Latest available version
• Account type: Personal Plus account

Steps to reproduce

1. Use Codex/ChatGPT normally.
2. Check Codex usage dashboard.
3. Compare displayed token usage with remaining weekly quota.

Expected behavior

The consumed quota should roughly correspond to the token usage shown in the Codex usage dashboard.

For example, 50k-60k tokens of usage should not consume almost the entire weekly Codex quota.

Actual behavior

Today:

• Codex usage dashboard shows approximately:
  • 59k tokens used

• However:
  • Weekly Codex quota dropped from around 50% remaining to almost 0%
  • I had to use a quota reset because the limit was unexpectedly reached

The quota consumption appears significantly higher than the displayed token usage.

Additional information

I initially suspected this was related to the ChatGPT macOS application, because I noticed quota decreasing while using Chat mode.

However, after testing, the same behavior appears to happen in the web version as well.

Therefore this does not seem to be limited to the desktop application.

Screenshot

Attached screenshot shows the usage dashboard displaying only ~59k tokens used while the weekly quota was nearly exhausted.

Questions

• Does Codex quota include hidden reasoning tokens, tool calls, context replay, or other internal usage that is not shown in the dashboard?
• Is there a known issue where quota consumption is incorrectly calculated?
• Could the usage dashboard be showing incomplete token accounting?

Thanks.

What steps can reproduce the bug?

just use

What is the expected behavior?

No response

Additional information

No response