Weekly allowance reaches its limit much sooner after reset despite using the same model
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
After my weekly Codex / ChatGPT Work allowance resets, I now reach the usage limit noticeably sooner than I did previously. I use exactly the same model before and after the change.
This report concerns the weekly allowance, rather than the five-hour window or a conversation's context capacity.
Confirmed observations
- The weekly allowance has reset before the faster depletion is observed.
- I reach the usage limit noticeably sooner in the new weekly window compared with previous usage.
- The model used before and after is identical.
Details not yet recorded
The exact model label, affected client/version, reset date and time, whether the reset was scheduled or redeemed/purchased, reasoning effort, Fast setting, and before/after usage measurements are not yet included. Comparable task volume and context size have not been established. Please do not infer that all of these variables were unchanged or that I purchased a reset.
This is a qualitative user observation, not a measured claim of a specific multiplier or proof of a billing/accounting fault.
Investigation requested
Please advise how to submit account-specific diagnostics privately, and investigate whether:
- The full expected weekly entitlement was restored.
- Any entitlement or metering changes could explain the difference.
- Unexpected background usage or a usage-accounting issue contributed to the faster depletion.
If abnormal deductions are confirmed, please review whether the affected allowance can be restored.
Related reports
- #44894: Another user reports faster weekly depletion after reset while comparing the same model.
- #42127: Another user reports faster weekly depletion following a reset.
These have similar symptoms; I am not claiming a confirmed shared root cause.
中文说明
我的每周额度重置后,现在明显比以前更快达到使用上限。前后使用的模型完全相同。请核查周额度是否完整恢复、计量规则是否有变化,以及是否存在异常后台消耗或额度扣减问题,并告知如何通过私密渠道补交账户诊断资料。
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
No repository file, test, or entry point is identified. Start by reviewing the requested account-specific diagnostics and the related reports in issues #44894 and #42127; the investigation is complete when entitlement restoration, metering or background usage, and any possible allowance restoration have been assessed.
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