openai / openai/codex

Usage UI is misleading when weekly limit is exhausted but 5-hour limit shows remaining allowance

Open
#46,384 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App MAC

What feature would you like to see?

In the Work/Codex usage screen, the 5-hour limit can show a large amount of remaining allowance while the weekly limit is already exhausted.

Example:

5-hour limit: 99% left
Weekly limit: 0% left

In this state, Work/Codex cannot be used because both limits must have remaining allowance.

This makes the UI misleading: it shows 99% left on the 5-hour limit, while the effective usable allowance is actually 0%.

Suggested improvements:

Show a clear message such as “Blocked by weekly limit”
Gray out or disable the 5-hour allowance when the weekly limit is exhausted
Or show something like “99% remaining, currently unavailable due to weekly limit”

This would make it much clearer why Work/Codex cannot be used even though the short-term usage meter appears almost full.

Screenshot attached.

Additional information

No response

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

Start by locating the Work/Codex usage screen and the rendering for the 5-hour and weekly allowance values. Reproduce the reported state with 99% remaining for the 5-hour limit and 0% for the weekly limit, then make the unavailable state explicit in the UI. Done means users can understand that Work/Codex is blocked by the exhausted weekly limit.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.