[Pro 20x] 5-hour limit exhausted while weekly usage increased by only 15%

What version of Codex are you using?

Latest available Codex version as of July 11, 2026. I can provide the exact build number and diagnostic information if needed.

What subscription do you have?

ChatGPT Pro with the 20x Codex usage allowance.

What platform is your computer?

macOS.

What issue are you seeing?

The 5-hour usage limit was completely exhausted even though only approximately 15% of my weekly limit had been consumed.

This indicates a serious discrepancy in quota accounting. Based on the expected relationship between the two limits and my previous usage behavior, exhausting 100% of one 5-hour window should correspond to approximately 20% of the weekly allowance, not only 15%.

Observed behavior:

• 5-hour limit used: 100%
• Weekly limit used: approximately 15%
• Subscription: Pro 20x
• Result: Codex became unavailable because the 5-hour limit was reached substantially earlier than expected.

The mismatch suggests that the 5-hour meter may be over-counting usage, applying a different or incorrect multiplier, double-counting requests/retries, or using an allowance that is smaller than the one associated with the Pro 20x plan.

This is a severe problem for a Pro 20x subscriber because the short-window limit is preventing access well before the corresponding weekly allowance has been consumed.

What steps can reproduce the bug?

1. Sign in to Codex with a ChatGPT Pro account that has the 20x usage allowance.
2. Begin with both the 5-hour and weekly limits available.
3. Use Codex normally during a coding session.
4. Monitor both quota meters.
5. Observe that the 5-hour limit reaches 100% usage while the weekly meter has increased by only about 15%.
6. Codex then blocks further use because the 5-hour limit is exhausted.

This may depend on server-side, account-specific quota accounting, so it may not reproduce consistently on every account.

What is the expected behavior?

The 5-hour and weekly limits should be deducted consistently according to the Pro 20x entitlement. If one complete 5-hour allowance is exhausted, the corresponding weekly usage should be approximately 20%, rather than only 15%.

At minimum, the product should provide a transparent usage breakdown showing which requests, models, tool calls, retries, cached tokens, or background operations caused the deduction. Failed requests and automatic retries should not be counted multiple times.

Additional information

Observed on July 11, 2026.

This appears related to other open quota-accounting reports, including #29963, #30212, #30002, and #28823. My report highlights the specific numerical inconsistency between the two meters on a Pro 20x account: 100% of the 5-hour limit versus only 15% of the weekly limit.

Please investigate the server-side quota calculation and confirm that the account is receiving the correct Pro 20x short-window allowance. I can provide account-specific diagnostics, session IDs, screenshots, or feedback IDs privately if the maintainers specify a safe channel.