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

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #38019

Powered by Codex Action

Pro 20x user checking in 🙋
Honestly, this feels even worse than “20x being billed like 5x.”
From what I’m seeing, it’s more like a weekly allowance is being burned as if it were a 5-hour allowance.

At this rate, “20x” is starting to look less like a multiplier and more like a speedrun category. 😅

Another independent Pro 20x reproduction, with a controlled time window and local token telemetry.

I am subscribed to the $200/month ChatGPT Pro 20x tier. My local Codex metadata still reports:

plan_type: "pro"

However, after my weekly window reset on Aug 13, the effective weekly capacity became dramatically smaller than my historical experience under a similar workflow.

Controlled interval

OpenAI Support confirmed that my main Codex weekly window had 18% remaining at:

2026-08-14 18:15:11 UTC+8

By approximately:

2026-08-16 09:00:00 UTC+8

the same weekly window had reached 0% remaining.

I parsed my local ~/.codex/sessions/**/rollout-*.jsonl telemetry for exactly that interval, using deltas of cumulative total_token_usage rather than summing repeated cumulative values.

Local activity during the 18% -> 0% interval

GPT-5.6 Sol

total_tokens            11,963,774
input_tokens            11,934,579
cached_input_tokens     11,495,680
uncached_input_tokens      438,899
output_tokens               29,195
reasoning_output_tokens     10,240

GPT-5.6 Terra

total_tokens            11,650,801
input_tokens            11,608,034
cached_input_tokens     10,520,576
uncached_input_tokens    1,087,458
output_tokens               42,767
reasoning_output_tokens     16,646

Combined

total_tokens            23,614,575
input_tokens            23,542,613
cached_input_tokens     22,016,256
uncached_input_tokens    1,526,357
output_tokens               71,962
reasoning_output_tokens     26,886

So approximately 93.5% of input tokens were cached input.

This was not a Fast-mode or image-generation workload:

• Fast mode: No
• Image generation: No
• Voice-initiated Codex tasks: No
• GPT-5.3-Codex-Spark usage was negligible and is tracked in its separate window

Using the published short-context token/credit rates, the locally observed activity is only on the order of a few hundred credits (roughly ~340–370 depending on the applicable Terra rate table), yet it coincided with depletion of the final 18 percentage points of the weekly Pro 20x window.

I understand local telemetry is not the authoritative server-side usage ledger, and there may be additional shared/background usage not visible locally. That is exactly what I would like the Codex team to help reconcile.

This seems closely aligned with this issue: the account still identifies as pro, while the effective quota allocation / denominator appears much smaller than the expected Pro 20x tier.

Could the team please check whether some $200 Pro 20x accounts are receiving an incorrect effective weekly quota after reset, or whether there is hidden server-side usage/accounting (retries, subagents, background activity, shared agentic usage, delayed reconciliation, etc.) that would explain this discrepancy?

A per-session/server-side credit deduction view would also make this class of issue much easier to diagnose.

Related detailed report: #38367.

Fresh Pro 20x reproduction after a new weekly reset: the meter fell to 46% remaining (~54 pp consumed) within ~11 hours, while the entire local Aug 20 Codex activity was only ~14.10M GPT-5.6 Terra tokens, corresponding to roughly <=117 published-rate credit-equivalent activity (and that is an upper bound because the daily report includes usage before the weekly reset time).

I posted the full token reconciliation and specific server-side questions in #38367. This again appears consistent with an effective quota denominator / entitlement or server-side accounting mismatch rather than visible local workload alone.

I think I’m seeing the same issue on my Pro 20x account.

My account still shows plan_type: pro, but the actual Codex quota feels much smaller. I checked the analytics data and the numbers are very consistent.

I used:

daily credits / daily usage percentage × 100

and got basically the same result every day:

• Aug 13: 19,976 credits / 48.80% → ~40,932
• Aug 14: 4,443 / 10.86% → ~40,932
• Aug 15: 11,018 / 26.92% → ~40,932
• Aug 16: 13,049 / 31.88% → ~40,932
• Aug 17: 7,793 / 19.04% → ~40,932
• Aug 18: 6,076 / 14.84% → ~40,932
• Aug 19: 3,333 / 8.14% → ~40,932

I’m paying for the $200 Pro 20x tier, but recently the weekly quota has been going down extremely fast. After the latest reset, I casually ran some Codex/Work tasks and already used around 10% of the weekly limit.
Would be great if someone from OpenAI could check the actual entitlement assigned to affected Pro 20x accounts.

Same issue here, I've subscribed to Pro 20x account, but seems receive only Pro 5x Codex usage recently.

Same issue here. I max out the usage this week. Do not use any reset or get any rest. The token usage shows a much lower weekly usage spending compare to last week