[macOS] Limit banner uses weekly reset despite weekly usage showing 69% remaining
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using?
26.825.41651
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Darwin 25.4.0 arm64 arm
What issue are you seeing?
This is a display/state-consistency issue. I did not lose access to Codex.
The Usage panel showed:
- 5-hour limit: 100%, reset at 03:27
- Weekly limit: 69% remaining, reset on September 6 at 11:15
However, the conversation banner said:
You have reached the usage limit. Upgrade or add credits to continue, or try again after September 6, 2026, 11:15.
The banner used the weekly reset time even though the weekly allowance showed 69% remaining. Codex remained usable afterward.
What steps can reproduce the bug?
- Open Codex Desktop and view the Usage panel.
- Reach the 5-hour usage limit.
- Confirm that the weekly allowance still has remaining usage.
- View the usage-limit banner in a conversation.
- Observe that it directs the user to wait for the weekly reset time instead of the 5-hour reset time.
- In this occurrence, Codex was still usable afterward.
What is the expected behavior?
When only the 5-hour limit is exhausted, the banner should show the 5-hour reset time.
If Codex remains usable, it should not display a misleading full-limit message that points to the weekly reset date.
Additional information
- Screenshot attached.
- Occurred on 2026-08-30, Asia/Shanghai time zone.
- Codex model used to prepare this report:
gpt-5.6-sol. - Local Codex CLI version:
0.144.4. - This report was drafted with assistance from OpenAI Codex Desktop and manually submitted by the affected user through their GitHub account.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the mismatch in Codex Desktop through the Usage panel and conversation limit banner. Trace how the 5-hour and weekly reset states are selected, then verify that the banner uses the exhausted limit's reset time and does not claim the full limit when usage remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100