openai / openai/codex

Pro 20x weekly quota consumption increased dramatically after reset

Open
#40,527 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

I’d like to report a possible issue with Pro 20x Codex usage limits after the latest weekly quota reset.

Yesterday, I used roughly $200 worth of Sol usage and my weekly quota dropped by about 20%. Before the reset, a similar amount of usage would normally consume only a little over 10%.

Today, I used only about $20 worth of Sol, yet my quota dropped another 4–5%. This suggests that my effective quota after the reset may be significantly lower than it was before.

I’ve been subscribed to Pro 20x for quite some time, and this is the first time I’ve seen my quota burn this quickly.

Could you please investigate whether the quota allocation or usage-accounting method changed after the latest reset? I’m also concerned there may have been some kind of quota rebalancing across Pro 20x accounts—for example, reducing quota on previously normal accounts while correcting accounts that had abnormally low limits.

I’m not claiming this is definitely what happened, but the change in consumption rate is large enough that I’d appreciate clarification.

Please check whether there were any recent changes to Pro 20x quota allocation or accounting, especially around weekly resets.

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

Start with the reported before-and-after usage figures and the timing of the weekly quota reset. Compare Pro 20x quota allocation and usage-accounting behavior around resets, including any recent changes. Done means the accounting behavior is confirmed or a reproducible discrepancy is identified.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.