5-hour usage limit decreased without running any task while daily graph shows 0 tokens

Open 💬 7 comments Opened Jun 26, 2026 by BalamEduardo
💡 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)?

26.623.12021

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

My Codex 5-hour usage limit decreased even though I did not run any Codex task today.

Today I opened Codex, but I did not:

  • start a task
  • send a prompt
  • run code
  • use the CLI
  • use the IDE extension
  • intentionally leave any task running

However, my usage panel shows that my 5-hour Codex limit dropped to 68% remaining.

The confusing part is that the daily usage graph shows 0 tokens for June 26, while the 5-hour usage limit still decreased. This seems inconsistent: if no task or token usage happened today, I do not understand why the 5-hour quota changed.

What steps can reproduce the bug?

I do not have a reliable code snippet to reproduce this, because the issue happened from the Codex app/usage tracking UI.

Steps observed:

  1. Open Codex.
  2. Do not start any task.
  3. Do not send any prompt.
  4. Do not run code.
  5. Check the usage panel.
  6. The 5-hour usage limit shows reduced usage remaining, even though the daily graph shows 0 tokens for the day.

Current usage shown in my account:

  • 5-hour limit: 68% remaining
  • Weekly limit: 95% remaining
  • Daily graph: 0 tokens on June 26
  • 5-hour reset shown: 21:17
  • Weekly reset shown: July 3
  • Available resets shown: 3

What is the expected behavior?

Opening Codex without starting a task, sending a prompt, or running code should not consume the 5-hour usage limit.

If the 5-hour usage limit decreases, the usage dashboard should show the corresponding activity or token usage that caused it.

The 5-hour usage limit and the daily usage graph should be consistent with each other.

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 24 days ago

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

  • #29195
  • #30234
  • #28908
  • #30081

Powered by Codex Action

BalamEduardo · 24 days ago

Thanks for the duplicate check.

I reviewed the suggested issues, especially #29195 and #30234. My issue looks closely related, but I’m leaving it open for now because my case includes a clear mismatch between the 5-hour usage limit and the daily usage graph:

  • The 5-hour Codex limit dropped to 68% remaining
  • The daily usage graph shows 0 tokens for the same day
  • I only opened Codex and did not start any task, send any prompt, or run code

If maintainers consider this a duplicate of #29195 or #30234, feel free to close it. I mainly wanted to provide another data point with screenshots showing the inconsistency.

carida-note · 24 days ago

Same Issue with me!

After not using Codex since yesterday afternoon except for about two turns, I opened the Codex app this morning and the 5-hour usage showed 92%.
I quit and relaunched the Codex app, and it then showed 90%.
I did not start a new Codex task, run tests, or ask the agent to modify code during this period.

thefujunjie · 23 days ago

MEMORY

TianZuo555 · 23 days ago
MEMORY

Nope, memory and ambient suggestions are both set as FALSE but Codex usage still draining

krevoit · 23 days ago

Same issue here, no flows or agents running, and no memory. 5h usage always starts at 99%, and today it drained down to 88% after just opening the app.

Valla56 · 22 days ago

Same issue. My remote connection kept coming up with a notification saying codex was working on something and I can see nothing is being worked on. I lost at least 30% of my 5h limit doing nothing while watching it go down rapidly.

I forgot I got a popup earlier asking to turn on Suggested prompts and it didnt mention anything about token usage to I decided to try it.
Turned it off and my usage stopped dropping.

Suggested prompts was my issue. At the very least warn users its going to burn through tokens. However, for it to use useful you should be able to customise it if its going to use that many tokens, not to mention the environmental impact this caused for nothing.