Codex Usage going up with no messages

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

What issue are you seeing?

My 5 hour window has been dropping despite no messages being sent. Simply logging in and opening the Codex app caused a 40% usage drop.

The Codex analytics dashboard shows the same 40% drop, but also shows no usage for June 20th.
<img width="621" height="414" alt="Image" src="https://github.com/user-attachments/assets/b3caee83-a561-4cff-bad4-4471c6295f18" />

Yet:
<img width="1237" height="376" alt="Image" src="https://github.com/user-attachments/assets/5dad6199-f130-41bb-8631-e90c2f792a3f" />
<img width="1237" height="438" alt="Image" src="https://github.com/user-attachments/assets/79b69ccf-a4c8-418c-b184-fce9b88320ce" />

What steps can reproduce the bug?

  1. Log out of Codex app.
  2. Log into Codex app.
  3. See your 5 hour window magically disappear.

What is the expected behavior?

No usage should drop until a message is sent, and limits shouldnt drop 40% just by opening the app.

Additional information

Note that the 5 hour window began on June 20th, 1:07 pm (as proven by resetting at 6:07 pm), which is when the app was opened. despite no message being sent also being reflected in the Codex analytics dashboard.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

  • #27788
  • #28908
  • #28896
  • #28694
  • #28687

Powered by Codex Action

mohammad-malik · 2 months ago

Note that the CLI does not seem to be affected.

Necmttn · 2 months ago

Quota drops without user messages need charge receipts by origin. Split foreground prompts from background startup, plugin sync, MCP init, thread resume, index rebuild, retry, and server-side adjustment.

For each quota-window delta, record timestamp, request id if any, client surface, model, quota units charged, token buckets when available, and origin. Then the UI can say "40% used by background plugin startup" or "server-side adjustment" instead of making users infer from an empty message history.

---

_Generated with ax._