Repository navigation
Weekly usage limit refresh dates seem to be variable #7354
Description
What version of Codex is running?
0.63.0
What subscription do you have?
plus
Which model were you using?
5.1 extra high
What platform is your computer?
win 11 wsl2
What issue are you seeing?
Starting work today my weekly limit had about 25% left, and the small, critical text under it at https://chatgpt.com/codex/settings/usage said it resets in 2 days on 11/29. I had a "hard" for it to work on and figured with that much time left I could fire it up on the heaviest model.
As the % ticked down to about 15, the weekly refresh date was pushed out another 5 days, to the first week of december.
When I killed the cli tool it bounced back to 11/29.
This.. can't be how you're doing business, right?
What steps can reproduce the bug?
Use what we pay for, a lot, apparently.
What is the expected behavior?
Consistent refreshes that don't change. Ideally, rate limits should refresh hourly not weekly in a consistent manor, but that's probably not your business model.
Additional information
😑
Activity
github-actions commentedon Nov 27, 2025
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Nov 27, 2025
Thanks for the bug report.
The fact that you saw the weekly refresh rate jump by five days and then bounce back does sound like a bug. It's likely that this was just a client-side (display) issue rather than a backend accounting issue, but we will need to investigate further to determine the cause.
Could you do me a favor and restore that session using
codex resume, then use/feedbackto upload the session and post the thread ID here? That will help us investigate.This is a holiday week in the U.S. (Thanksgiving), and most of the Codex team is on break spending time with their families. We'll dig into this next week when the team is back from vacation.
cozuya commentedon Nov 28, 2025
I've done that now and it gave me this id to give back
019ac6e1-c815-7151-ab37-ae757a7e7986thanks. The websocket was probably long lived so could have been something odd there, hadn't moved from that page.aehlke commentedon Nov 29, 2025
I'm also seeing this. It bounced from Nov 29 to Dec 2 a few days ago, and then it fixed itself and showed Nov 29 again. But now today, it is saying Dec 2 again (without having reset the limit).
I checked on the web and it also says: Resets Dec 2, 2025 3:16 AM
My last reset date was a week ago. I've almost run out of quota as it was telling me it would reset today and that it was a "weekly limit" instead of a 10 day limit. I hope I'm not unable to use my Pro subscription for the 3 days it has extended the limit by... That is 10% of the period I paid for. Support has not been helpful with this case. I hope this is an urgent priority next week as it will run out before your team is back from holidays. Thank you
aehlke commentedon Nov 29, 2025
Here is my thread ID: 019ace65-d780-7a93-b1ed-68c4edd7948e
aehlke commentedon Nov 29, 2025
And mine just recovered again...
mpakunderscore commentedon Dec 1, 2025
Over the past four hours, my "Weekly usage limit" counter has switched from 80%+ to 0 and back four times.
I also saw a message about missing tokens in the Cursor plugin. So, I suspect this isn't a client bug. The client currently shows 80%+, and there's no message about insufficient tokens in the cursor.
mpakunderscore commentedon Dec 1, 2025
Right now the Cursor plugin shows "You're out of Codex messages. Buy more to continue, or wait until 12/2/2025, 1:41:25 AM. Buy more."
However, everything is fine in the client.
Weekly usage limit
80% remaining
5 hour usage limit
35% remaining
etraut-openai commentedon Dec 3, 2025
Here's a quick update on this issue. We believe we understand the problem. Earlier today, we took the first step toward mitigation by resetting the limits for everyone in Codex. This was the fastest and least-risky way to eliminate the worst of the inconsistencies that some Codex users were seeing. We plan to roll out additional fixes over the coming days. I'll keep this issue open until we have all of those fixes in place.
nuliknol commentedon Dec 4, 2025
@etraut-openai is Web interface GUI (not Codex Web GUI , just regular prompt in ChatGPT web) shared with Codex cli? Because I was heavily using web interface (for architecture design, with coding samples), and when I logged into my codex cli interface I see: 95% usage, but I only used it once since week started. I wonder if you use web prompting will affect your codex-cli usage?
etraut-openai commentedon Dec 4, 2025
@nuliknol, yes, usage limits are shared across all Codex interfaces (CLI, IDE extension, and web).
cozuya commentedon Dec 20, 2025
Bump? I mean this big 0 to 100% bar (for both overall and code review) is pretty big part of my workflow now. I know its only $20/mo, but I try to get the most use out of it. 3 hours ago my code review was at 0% and my overall a bit above, with refresh dates days away. For funzies I hit the bookmark now, tonight, and they're both reset, days in advance? So now I have to work tomorrow.
At the very least, can you provide a email, or hopefully much better than that, notification/alert in some way that our limits have reset? Magically, apparently?
etraut-openai commentedon Jan 5, 2026
I mentioned previously that we put in place a short-term mitigation for the variability that some users were seeing in their refresh dates and available usage. We've completed the rollout of a permanent and robust solution to this problem, so I'm going to close this bug.
rebroad commentedon Mar 9, 2026
I just saw my weekly limit drop from 27% to 0% in the space of about 5 minutes, without ANY USAGE. I even did a "log out of all sessions" to ensure there were no other usages happening, which did refresh the auth.json to a new cookie. Yet the problem persisted. The (weekly limit % left) seemed to start dropping when I entered a partial prompt in Cursor (within the Codex extension), but without sending the prompt, and before I even got the chance to send a prompt, it told me I was out of credits!