Weekly quota reset date moved forward
What version of Codex is running?
v0.64.0-alpha.10
What subscription do you have?
Pro
Which model were you using?
gpt-5.1-codex-max
What platform is your computer?
macOS
What issue are you seeing?
Context window: 100% left (0 used / 272K) │
│ 5h limit: [████████████████████] 100% left (resets 13:28) │
│ Weekly limit: [████░░░░░░░░░░░░░░░░] 18% left (resets 12:37 on 2 Dec)
For four days I kept seeing weekly quota ending on the 30th of Nov at 7am (today) and now suddenly it says ending on 2nd Dec? Why?
What steps can reproduce the bug?
Uploaded thread: 019ad302-f73a-7d62-adb8-c4ad0e63409f
What is the expected behavior?
It should have reset today
Additional information
No response
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
- #7354
- #7325
- #7255
- #6429
- #5999
Powered by Codex Action
This happened to me and its a bug with the cli. I checked my web dashboard and its correct
There is some major problem with Codex usage. In my IDE (VS Code), it the rate limits remaining constantly fluctuate between 0% remaining and my actual. It's intermittent, and I get the warning message that I'm out of messages. The web UI and command prompt are all inconsistent too - checking codex /status in the command line yields I have 5h limit - 74% left, weekly limit - 92% left while VS Code and the web portal show I have 0% left.
At the moment, my command line shows me 92% left for the week and the reset date is Dec 7th. In VS Code and the web portal it shows 0% and Dec 2.
The period in which it changes is frequent enough, I can see it change every few minutes, sometimes once per 30 minutes or so. I think this is a bug - maybe they have different systems calculating usage limits that are not consistent (no source of truth). I'm unsure which is correct, but I have to think the Dec 7th date for me is, since I can still actually post messages and it seems to work.
Funny, I now keep seeing
⚠ Heads up, you've used over 75% of your weekly limit. Run /status for a breakdown.
when
Context window: 96% left (21.7K used / 272K) │
│ 5h limit: [███████████████████░] 94% left (resets 13:07) │
│ Weekly limit: [███████████████████░] 94% left (resets 08:35 on 7 Dec)
And now I'm seeing
⚠ Heads up, you've used over 90% of your weekly limit. Run /status for a breakdown. yet
Context window: 96% left (21.7K used / 272K) │
│ 5h limit: [██████████████████░░] 89% left (resets 13:07) │
│ Weekly limit: [██████████████████░░] 92% left (resets 08:35 on 7 Dec)
I have a feeling the first warning is correct.
And...
Context window: 78% left (68.1K used / 272K) │
│ 5h limit: [████████████████████] 98% left (resets 18:24) │
│ Weekly limit: [██░░░░░░░░░░░░░░░░░░] 9% left (resets 12:37 on 2 Dec)
Well mine was correct and had set itself to the correct value yesterday after incorrectly saying my usage was almost used up (despite having just reset the day before)
Now today the vscode plugin says i'm at 0% and the dash in the web says i'm at 0% but the codex cli says i'm at 84%
So its always either the webdash/plugin are correct and the cli is wrong or its the opposite
Some major sync bug happening between all these systems atm
Same issue here, CLI and the Visual Studio Code plugin show an incorrect weekly usage and reset date. My real usage is as the dashboard shows.
well now I'm really confused...
@NYPDK i'm getting the same kind of thing. For me it keeps switching between the cli being correct and dash/plugin being wrong and then vis versa. Really strange. You'd think these would all just be hitting the same endpoint
@smaccoun Perhaps the CLI/VSC plugin use some kind of caching that is flawed? I really have no clue.
The Codex web client and Cursor plugin are receiving token shortage messages today. I have tokens. The messages are out of sync (sometimes they appear together, sometimes separately).
I'm going to close this issue in favor of #7354 and post updates there.