openai / openai/codex

100% Remaining but still its showing that I have exhausted the Weekly Limit

Open
#42,300 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug extension rate-limits windows-os
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?

GPT Plus

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?
Image

100% of my quota is still remaining, yet it’s showing that I’ve already used my weekly limit. This honestly feels like a fraud.

And now that 5.4 has been retired, the usage on 5.5 Medium seems to be 100× higher than 5.4. Bruh, what’s actually happening here? 😭 Is OpenAI seriously doing this to us?

What steps can reproduce the bug?

Whenever I am putting any Message Its showing that I have exhausted my limit..

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reproducing the quota warning in the VS Code extension version 26.825.51511 on Windows with a GPT Plus subscription, then trace how the displayed weekly limit is obtained and compared with remaining quota. Done means the usage state accurately reflects the available quota.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.