codex - 💡(How to fix) Fix Codex usage popover shows confusing remaining percentages for 5h vs weekly buckets

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

Because the row says “Usage remaining”, users reasonably interpret both percentages as remaining quota. Under that interpretation, 5h: 97% remaining and Weekly: 95% remaining during the first short-term window of the week feels wrong or under-explained.

Code Example

Current 5h window: 97% remaining
Weekly pool: 95% remaining
Includes all Codex usage across app, CLI, cloud tasks, reviews, and devices
Resets Jun 7

---

Weekly pool: 95% remaining
Rolling 7-day window, resets gradually

---

Usage remaining
5h      97%   6:23 PM
Weekly  95%   Jun 7
RAW_BUFFERClick to expand / collapse

What happened?

The Codex app usage popover appears to show both the short-term bucket and weekly bucket as remaining usage, but the numbers are confusing/inconsistent from a user perspective.

In the popover:

  • Usage remaining: 5h, 97%, timestamp 6:23 PM
  • Weekly: 95%, reset date Jun 7

The user expectation was that this was the first 5-hour usage window of the week. If both percentages are “remaining”, it is surprising that the current 5-hour bucket is still at 97% while the weekly bucket is already lower at 95%.

This may be technically explainable if the weekly bucket includes other Codex usage, a rolling 7-day window, usage across devices/workspaces, or a different accounting scope. But the UI does not explain that, so it looks like either a metering bug or a contradictory display.

Why this is confusing

The popover labels do not say whether the percentages mean:

  • percent remaining vs percent used
  • current 5-hour window vs all Codex usage
  • natural week vs rolling 7-day window
  • current workspace vs account-wide usage
  • local app vs cloud/CLI/other Codex activity

Because the row says “Usage remaining”, users reasonably interpret both percentages as remaining quota. Under that interpretation, 5h: 97% remaining and Weekly: 95% remaining during the first short-term window of the week feels wrong or under-explained.

Expected behavior

The UI should make the scope and semantics explicit. For example:

Current 5h window: 97% remaining
Weekly pool: 95% remaining
Includes all Codex usage across app, CLI, cloud tasks, reviews, and devices
Resets Jun 7

If weekly usage is rolling rather than calendar-week based, say that explicitly:

Weekly pool: 95% remaining
Rolling 7-day window, resets gradually

If the weekly pool can be lower because it includes usage outside the current 5-hour bucket, the popover should explain that.

Actual behavior

The UI shows compact rows like:

Usage remaining
5h      97%   6:23 PM
Weekly  95%   Jun 7

Without explanation, this looks internally inconsistent.

Environment

  • Product: Codex desktop app
  • Platform: Windows app
  • Date observed: 2026-06-01
  • Screenshot was taken from the in-app usage popover.

Related reports

There are existing usage/metering issues in this repo, but this report is specifically about the usage popover semantics and the confusing 5-hour vs weekly remaining percentages.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The UI should make the scope and semantics explicit. For example:

Current 5h window: 97% remaining
Weekly pool: 95% remaining
Includes all Codex usage across app, CLI, cloud tasks, reviews, and devices
Resets Jun 7

If weekly usage is rolling rather than calendar-week based, say that explicitly:

Weekly pool: 95% remaining
Rolling 7-day window, resets gradually

If the weekly pool can be lower because it includes usage outside the current 5-hour bucket, the popover should explain that.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex usage popover shows confusing remaining percentages for 5h vs weekly buckets