Weekly usage reset date advanced without restoring allowance
Nobody has claimed this yet.
- 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.810.52044
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
My weekly Codex allowance did not replenish at its scheduled reset.
I was watching the allowance because it was nearly exhausted and I was waiting for the weekly reset. The reset time passed, but the allowance never returned to 100%.
Instead, the reset date advanced by another week.
Current state:
Weekly limit: 6% left (resets 09:19 on 7 Sep)
I did not purchase, apply, or use an instant/banked reset.
The 5-hour limit is resetting normally; only the weekly limit is affected.
What steps can reproduce the bug?
This appears to be a server-side quota issue, so I cannot deliberately reproduce it.
Observed sequence:
- Weekly allowance became nearly exhausted.
- Waited for the scheduled automatic weekly reset around Aug 31 / Sep 1.
- Reset time passed.
- Weekly allowance did not replenish.
- Next reset date advanced to Sep 7 at 09:19.
Codex CLI version: 0.145.0
Current /status:
Weekly limit: 6% left (resets 09:19 on 7 Sep)
What is the expected behavior?
At the weekly reset, the allowance should return to 100% and the next reset date should advance by one week.
Instead, only the reset date advanced.
Additional information
OpenAI Support case: 14183590
Support suggested that delayed usage might have been applied after the reset, but has not confirmed from account usage records that the allowance actually reset to 100%.
I was actively monitoring the weekly allowance at the time and did not observe any replenishment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Codex CLI /status output and the reported weekly reset sequence; the issue names no repository file or test. Compare the displayed weekly allowance and reset date with the account usage records and Support case 14183590. Done means identifying why the reset date advances without restoring the allowance, or documenting the server-side evidence needed to confirm the failure.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100