Repository navigation
Weekly Codex quota reset/reconciliation appears broken — quota exhausted with no local activity #42660
Description
What issue are you seeing?
I appear to have hit a Codex weekly quota accounting/reset bug on ChatGPT Plus. I want to upgrade to Pro but these inconsistencies are blocking me.
Timeline (America/Chicago):
- Aug. 30: I legitimately used Codex.
- Last locally recorded activity was Aug. 30 19:37 CDT.
- At that point Codex's server-provided rate-limit data showed:
- 94% 5-hour usage
- 65% weekly usage
- weekly reset: Sep. 5 16:24 CDT
- Aug. 31: the ChatGPT usage UI instead showed approximately:
- 0% of 5-hour allowance remaining
- 37% of weekly allowance remaining / ~63% used
- weekly reset changed to Sep. 7 00:13 CDT
- I performed no intentional Codex work Aug. 31-Sep. 2 and paused my existing tasks.
- Sep. 1 account activity nevertheless showed approximately 62.3M tokens.
- By Sep. 2, the weekly allowance reached 0% remaining.
I inspected the local Codex state on the machine running Codex CLI 0.151.0:
Threads created or updated Aug. 31-Sep. 2: 0 2026-09-01: logs_2.sqlite rows=0 2026-09-02: logs_2.sqlite rows=0 2026-09-01: rollout_files_with_activity=0, token_count_events=0 2026-09-02: rollout_files_with_activity=0, token_count_events=0 Last local thread update: 2026-08-30 19:37:29 CDT Last server-provided rate-limit snapshot: weekly_used=65% weekly_reset=2026-09-05 16:24 CDT
The suspicious part is that the weekly reset anchor changed from Sep. 5 to Sep. 7 while usage apparently remained around 63–65%, rather than resetting, and then the remaining quota depleted despite no corresponding local Codex session activity.
This could be delayed reconciliation across a reset boundary, server-side activity not represented locally, or incorrect account-side usage attribution.
I have attached a sanitized diagnostic report generated from state_5.sqlite, logs_2.sqlite, and rollout metadata. It contains no prompts, responses, paths, UUIDs, repository names, or tool arguments.
Could someone check the server-side usage ledger around Aug. 30-Sep. 2 and determine what consumed the weekly allowance after the reset/window change?
What steps can reproduce the bug?
Doing nothing. My weekly quota got exhausted while I still have 100% 5hr limit with a full reset on September 7
What is the expected behavior?
My quota should not be draining when I'm doing nothing.
Activity
github-actions commentedon Sep 4, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
official-elinas commentedon Sep 4, 2026
Not a duplicate. Possibly related to #42280, which reports a weekly reset date advancing without replenishing the allowance. My case additionally includes local Codex telemetry from before and after the reset boundary and subsequent quota depletion with no corresponding local thread or rollout activity.
official-elinas commentedon Sep 4, 2026
Update as of today 2026-09-04 (was only using chat at the time yesterday NOT work to debug - no agentic usage)
I received another fresh reset on Sep. 3.
At approximately 21:44 CDT on Sep. 3:
Within minutes:
At 14:03 CDT on Sep. 4:
So the new weekly allowance went from 94% remaining to 37% remaining (~57 percentage points) in approximately 16 hours.
I have not intentionally performed anything resembling that amount of Codex/Work activity. This is now a prospective reproduction after a fresh reset, rather than only reconstruction of the previous Aug. 30-Sep. 2 incident.
The ChatGPT usage page explicitly identifies these meters as the Agentic usage limit.
There is another report filed today with a very similar symptom on Pro: #42765, where weekly usage reportedly dropped from ~45% to 0% despite no sessions being run.
I am deliberately not upgrading to Pro or purchasing credits while this remains unexplained, because the same behavior appears to affect Pro accounts as well.
official-elinas commentedon Sep 5, 2026
Further evidence. After an update with Astra now GA I have a banked reset. Great. What's not great? My credit continues to drain without any usage.
official-elinas commentedon Sep 5, 2026
Please check the server-side account ledger for:
At this point I am going to open a ticket and/or cancel my plan. This is terrible.
official-elinas commentedon Sep 6, 2026
After noticing my SSH remote Codex helper was stale and showed “restart to update,” I updated/restarted it on Sep. 5. Since that restart, the weekly meter has remained stable at 65% for several hours with no agentic activity. This may indicate the earlier drain was related to a stale remote app-server/helper, though I cannot confirm causation yet.
official-elinas commentedon Sep 28, 2026
Closing as this seemed to be some hanging process with the codex-server using the cli. It stopped draining weeks ago after I updated it. Forgot to close.