Pro 20x weekly Codex quota draining abnormally fast during small VS Code bug fixes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the IDE extension are you using?
26.825.51511
What subscription do you have?
ChatGPT Pro ($200/month, 20x Codex tier)
Which IDE are you using?
Visual Studio Code (VS Code)
What platform is your computer?
Windows 11, x64
What issue are you seeing?
My main Codex weekly quota is draining abnormally fast on ChatGPT Pro 20x while using the Codex VS Code extension.
I am currently working on release preparation for an existing Flutter application. Most of my recent work consists of small bug fixes, reviewing existing code, and release-related checks — not building a new application or performing major architectural work.
After the most recent global reset, I noticed the weekly quota dropping much faster than in previous weeks. Within roughly the first 4 hours it had already dropped to about 91% remaining, and around two hours later it was down to approximately 62%. The drain continued rapidly afterward, eventually reaching only 1% remaining.
This is dramatically higher consumption than I experienced previously on the same project with similar tasks.
I have used high/Extra High reasoning and had Speed/Fast mode enabled during part of the workload, so I understand those can increase usage. However, the observed rate still appears significantly higher than my previous experience on the same Pro 20x plan and project.
My concern is that there may be an issue with quota accounting or unexpectedly high usage consumption affecting the main weekly Codex allowance.
What steps can reproduce the bug?
- Sign in with a ChatGPT Pro 20x account in the Codex VS Code extension.
- Open an existing medium-to-large Flutter project.
- Use Codex for ordinary release work such as reviewing a few existing files, fixing small bugs, checking configuration, and validating release-related changes.
- Monitor the main weekly Codex usage percentage before and after several tasks.
- The weekly quota decreases disproportionately quickly compared with previous weeks, even though the work is mainly review and small fixes rather than large code generation or a full rebuild.
In my case, the quota went from near-full after a recent reset to ~91% remaining within about 4 hours, then to ~62% roughly two hours later, and continued falling rapidly until only 1% remained.
What is the expected behavior?
I expect the Pro 20x weekly allowance to decrease according to the actual workload and model usage, but at a rate reasonably consistent with previous weeks when performing similar tasks on the same project.
Small bug fixes and release reviews should not consume most of the weekly Pro 20x allowance within such a short period unless the workload genuinely warrants that level of consumption.
I would like the quota accounting to be reviewed to confirm whether the observed usage is expected or whether there is an incorrect-consumption bug.
Additional information
Plan: ChatGPT Pro ($200/month / 20x Codex tier)
IDE: VS Code on Windows 11 x64
Project: Existing Flutter/Dart application with a relatively large codebase and automated tests.
Usage type: Small bug fixes, code review, release-readiness checks, and some authorized external developer/service tooling.
The same project and broadly similar workflow consumed noticeably less weekly quota in previous weeks.
I can provide screenshots showing the weekly allowance falling to 9% and then 1% remaining after the recent reset.
Please investigate whether the main Codex weekly allowance is being accounted for correctly on Pro 20x accounts.
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 or test is named. Start by reproducing the reported quota changes in the Codex VS Code extension using the stated Pro 20x plan and Flutter workflow, then trace how usage is recorded and displayed. Done means confirming whether the consumption matches the workload or identifying and correcting an accounting discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100