[BUG][QUOTA TAX] new pro 20x accounts consume quota faster than old ones.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
newest
What subscription do you have?
20x
Which model were you using?
gpt6
What platform is your computer?
apple silicon
What terminal emulator and version are you using (if applicable)?
No response
Codex doctor report
What issue are you seeing?
I registered a new 20x account to try gpt-6 astra due to "selected model is at capacity" error few days ago. After a few days, it is very obvious that newly registered 20x account consumes quota much faster than experienced ones. Same workload, the new account consumes 1.5x to 2x faster than old account. Is new account designed to pay quota tax? Please fix.
What steps can reproduce the bug?
try same workload on new/old pro 20x accounts.
What is the expected behavior?
No response
Additional information
No response
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 source file, entry point, or test is identified. Start by reproducing the same workload with new and old 20x accounts, then compare their quota consumption while recording the model and platform details provided here. Done means the reported 1.5x–2x difference is explained and equivalent workloads no longer consume quota at different rates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100