Codex usage UI shows 65% 5-hour quota remaining while overall/weekly quota is 0% and access is blocked

What version of the Codex App are you using?

26.903.61454

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS, Apple Silicon

What issue are you seeing?

The Codex Desktop usage UI is internally confusing/inconsistent when the weekly quota is exhausted before the 5-hour quota.

Observed state on Sep 10, 2026:

• Top-level Remaining usage: 0%
• 5-hour: 65% remaining
• Weekly: 0% remaining
• Codex is blocked and shows: You're out of Codex and Work usage
• The UI says to wait until the weekly reset on Sep 15

No screenshot is attached intentionally.

The backend behavior may be expected if the 5-hour and weekly windows are independent constraints and either one reaching zero blocks further use. The problem is that the UI presentation strongly suggests that these percentages describe usable remaining capacity under one combined allowance.

From a user's perspective, seeing 65% remaining in the active 5-hour window implies that substantial usage is still available, while the product simultaneously says that no usage is available at all.

There are two reasonable ways this could be presented:

1. If the 5-hour percentage is intended to represent usable capacity under the current overall allowance, it should be normalized/scaled against the remaining weekly capacity. In that model, as the effective overall allowance approaches zero, the 5-hour meter should deplete proportionally faster and also reach 0% when no more work can be started.

2. If the two percentages are intentionally independent hard limits, the UI should make that explicit and clearly identify the blocking constraint, for example:

Usage unavailable
Weekly limit exhausted — resets Sep 15
5-hour limit: 65% remaining (cannot be used until weekly reset)

The current nesting under a single Remaining usage value makes it look like a meter/accounting mismatch rather than two independent gating windows.

Steps to reproduce

1. Use Codex on a Plus account until the weekly allowance reaches 0% while the current 5-hour allowance still has capacity remaining.
2. Open the account/usage popover in Codex Desktop.
3. Observe a state similar to:
   • Remaining usage: 0%
   • 5-hour: 65%
   • Weekly: 0%
4. Attempt to continue a Codex task.
5. Codex blocks execution because the weekly quota is exhausted.

Expected behavior

The usage UI should make the relationship between the 5-hour and weekly limits unambiguous.

Either:

• the displayed 5-hour percentage should reflect effective usable capacity and reach 0% when the overall allowance is exhausted;

or, if the limits are independent:

• keep both independent percentages, but explicitly mark the weekly limit as the blocking constraint;
• explain that the displayed 65% 5-hour allowance is currently unusable;
• avoid presenting the independent meters in a way that implies they should reconcile with the top-level Remaining usage percentage.

Actual behavior

The UI simultaneously presents:

Remaining usage: 0%
5-hour: 65%
Weekly: 0%

while Codex is completely unavailable.

This is especially confusing because the parent Remaining usage: 0% and the nested 5-hour: 65% appear to contradict each other unless the user already knows the internal quota-gating model.

Additional information

This report is about the usage-meter UX / relationship between the displayed quota windows, not a claim that the weekly limit itself was incorrectly exhausted.

Related discussions about quota transparency and the interaction between the 5-hour and weekly windows include #40524 and #41004.

Start from the Codex Desktop account/usage popover and the quota-gating state that produces “Remaining usage: 0%” alongside the 5-hour and weekly values. Reproduce the weekly-exhausted state described here and trace how the blocking constraint is selected and displayed. Done means the UI clearly explains why use is blocked and no longer presents the remaining meters as contradictory.