openai / openai/codex

ChatGPT Pro (20x) accounts appear to receive Pro 5x Codex usage capacity

Open
#38,157 10 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

Multiple active ChatGPT Pro accounts still show the paid Pro (20x) subscription, and the official Codex usage API continues to identify them as plan_type: "pro". However, their effective Codex usage allowance now behaves like the much smaller Pro 5x tier.

The issue is therefore not the displayed subscription name or the plan_type field. It is the amount of usable quota actually allocated to accounts that are still subscribed to Pro (20x).

Observed behavior
  • The affected accounts remain active ChatGPT Pro subscriptions.
  • The official usage response still reports plan_type: "pro".
  • Despite that, usage percentages rise and limits are reached at a level consistent with Pro 5x rather than the expected Pro 20x allowance.
  • This was observed across multiple separately subscribed Pro accounts, not just one account.
  • The change appeared at roughly the same time across the affected accounts.
Expected behavior

Accounts subscribed to ChatGPT Pro (20x) should receive the corresponding Pro 20x Codex usage allowance.

Actual behavior

The accounts are labeled and authenticated as Pro, but their effective Codex quota appears to be provisioned at approximately the Pro 5x level.

Request

Could the team please investigate the effective quota allocation for active Pro subscriptions, including whether some Pro 20x accounts were accidentally assigned the lower 5x allowance during a quota reset or entitlement rollout?

No account identifiers, email addresses, credentials, or private infrastructure details are included in this report.

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 files, tests, or entry points are named. Start by examining the official usage API responses for affected Pro accounts and compare the reported plan_type with the observed quota; done means determining whether active Pro subscriptions receive the expected Pro 20x allowance.

Written by the indexing model from the issue text.

Assessment

Domain
api, 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.