openai / openai/codex

[Pro 20x][Sep 9] Weekly quota jumped ~3% → 30% → 3%; Full reset attempt did not restore allowance

Open
#44,274 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What version of the Codex App are you using?

Current Codex Desktop on macOS, Apple Silicon. I do not have the exact build number.

What subscription do you have?

ChatGPT Pro — $200/month / Pro 20x.

What issue are you seeing?

I’m confused by a quota state I saw on September 9, 2026.

My weekly allowance was around 3% remaining. At approximately 12:35:53 PM CDT, the official Usage page showed 30% remaining. At approximately 12:42:35 PM CDT, it showed 3% remaining again.

The sequence was:

~3% remaining → 30% remaining → 3% remaining

I had Codex work running while the 30% state was visible. After the Usage page returned to the earlier state, I used a Full reset, but the weekly allowance still did not restore and remained around 3%. I do not know whether the reset request was accepted or not.

What steps can reproduce the bug?

I do not have a deterministic reproduction. This is the sequence I observed:

  1. Weekly allowance was around 3% remaining.
  2. The official Usage page showed 30% remaining.
  3. A few minutes later, it showed 3% remaining again.
  4. I used a Full reset after the state returned.
  5. The weekly allowance remained around 3%.
What is the expected behavior?

The Usage page should show one consistent weekly quota state. If a reset is used, the allowance should either restore consistently or clearly show that the request failed.

Additional information

The attached screenshots are timestamped official Usage captures showing the 30% and 3% states. I can provide additional account-specific details privately if needed.

My earlier, separate quota report is #42912:
https://github.com/openai/codex/issues/42912

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 repository file, test, or entry point is identified. Start by reviewing the Usage page and Full reset behavior around the reported 3% → 30% → 3% sequence; done means the weekly quota is displayed consistently and a reset either restores the allowance or clearly reports failure.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.