openai / openai/codex

Weekly Codex limit dropped from ~45% to 0% with no sessions run (Pro, Desktop app)

Open
#42,765 13 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From "About Codex" dialog)?
[26.901.31953

What subscription do you have?
ChatGPT Pro

What issue are you seeing?

My weekly Codex usage went from ~45% remaining to 0% remaining in a window where I ran nothing.

Timeline (CEST, Sep 4 2026):

  • ~10:00–11:00: Usage & billing showed roughly 45% left on the weekly limit
  • ~12:00–13:00: same page shows 0% left, reset Sep 7 2:05 PM
  • No Codex sessions, cloud tasks, or background runs between those checks. Desktop app only; no CLI, no IDE extension, no web.

Evidence that nothing consumed it on my side:

  • Analytics > Usage history shows a near-zero Codex bar for Sep 4. Heavy days were Aug 31 and Sep 1.
  • GPT-5.3-Codex-Spark 5-hour window still at 100% left (resets 6:31 PM), so nothing ran on that model this morning either.
  • No Work / Excel / agent usage on this account in the last 7 days. [adjust if not true]

Support case 14377883 has given two AI replies asking for more details and stating limits can't be reset; nothing has been investigated. Opening here so the metering team can see it.

What I'd like: an explanation of what was attributed to my account between 10:00 and 13:00 CEST, and whether this is a metering or attribution bug. I have 2 reset credits and am holding them until this is understood.

Screenshots attached: Usage & billing (0% weekly, Spark 100%), Analytics (flat Sep 4), out-of-usage banner.

Image Image Image Image Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides a desktop-app usage timeline, Usage & billing and Analytics screenshots, and support case 14377883. Start by reviewing how weekly Codex usage is attributed between the reported checks and compare it with the near-zero Sep 4 history. Done means identifying the attributed usage and determining whether the discrepancy is a metering or attribution bug.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.