Repository navigation
Weekly usage limit was exhausted after about 15 hours of use #15166
Description
What version of the IDE extension are you using?
v26.313.41514
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
The extension reports that my weekly usage limit was exhausted after about 15 hours of use, which seems much earlier than expected for a Plus subscription.
I was using the extension normally in VS Code, and after around 15 hours I hit the usage cap for the week. I did not expect the weekly limit to be consumed that quickly.
The issue is that either:
- usage is being counted incorrectly,
- the weekly quota is much lower than expected,
- or the quota policy is not clearly communicated in the extension.
What steps can reproduce the bug?
- Install and use the IDE extension in VS Code with a Plus subscription.
- Use the extension normally for coding assistance over the course of about 15 hours.
- Continue making requests until the extension reports that the weekly usage limit has been exhausted.
- Observe that the weekly limit is reached much earlier than expected.
I do not have a minimal code snippet because this does not appear to be project-specific. The problem seems related to quota accounting / usage tracking rather than a specific codebase.
What is the expected behavior?
The weekly usage limit should be tracked accurately and should not be exhausted after only about 15 hours of normal use unless that is explicitly the intended policy for the Plus plan.
If this behavior is expected, the extension should clearly communicate:
- how usage is counted,
- what the actual weekly quota is,
- and why the limit was reached so quickly.
Additional information
This looks more like a quota/accounting or product-limit issue than a code-related bug.
It would be helpful to clarify:
- whether usage accounting is working correctly,
- whether Plus has a specific lower IDE-extension quota,
- and whether there is a way to see detailed usage consumption inside the extension.
I can provide screenshots or exact timestamps if needed.
Activity
github-actions commentedon Mar 19, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
4erdenko commentedon Mar 19, 2026
I’m having the same issue here. I have a work account with a Plus subscription, and in just one or two days I completely used up my limits. No matter which reasoning level I use, the limits get consumed very quickly. I don’t have any special MCP settings enabled, just a few standard ones that I’ve always had. I also haven’t noticed any additional token load.
I don’t understand what’s going on, but so far no one has responded to these messages. What’s more, when some users experienced faster limit depletion last week and the developers responded to it, I wasn’t part of that group and didn’t have that issue at the time. But now it’s definitely happening on two different mega accounts. The same thing is happening on the trial subscription. The usage there is a bit slower, but it’s still faster than it used to be.
dturovskiy commentedon Mar 19, 2026
The main question is what we are supposed to do about this.
OpenAI either is not really addressing it, or at least there has been no visible progress so far.
I received an email saying that my report may be a duplicate:
“Potential duplicates detected. Please review them and close your issue if it is a duplicate.”
Related issues:
It also looks like we are clearly not the only ones experiencing this. Multiple users have already reported very similar rate limit / usage metering problems, but there still does not seem to be any clear fix, workaround, or meaningful update.
The large weekly limits were exactly the reason I chose Codex in the first place. But in its current state, it may make more sense to switch back to Claude, because even there the limits felt more usable and predictable than what we are seeing here now.
openresearchtools commentedon Mar 19, 2026
This is the main ongoing current thread for this #14593