openai / openai/codex

Weekly usage meter showed 25% remaining, then unexpectedly reached the limit

Open
#44,941 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What version of Codex CLI is running?

Installed CLI: 0.154.0; issue observed in the desktop app

What subscription do you have?

Pro

Which model were you using?

Not recorded; please see the uploaded thread.

What platform is your computer?

macOS — Darwin 25.4.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Not applicable — Codex desktop app

Codex doctor report
Not collected.
What issue are you seeing?

My weekly usage meter showed approximately 25% remaining, but shortly afterward I unexpectedly reached the weekly limit. The sudden change made it difficult to understand how much usage I actually had left.

Please investigate whether the displayed remaining allowance was delayed or inaccurate, or whether actual usage consumed the remaining allowance. I do not have enough information to determine the cause.

What steps can reproduce the bug?

Uploaded thread: 01a08331-7203-7d53-9fc3-e30dd17f9e12

What is the expected behavior?

The weekly usage indicator should accurately reflect the remaining allowance. If usage reporting is delayed or substantial usage is still pending, that should be clearly indicated before the limit is reached.

Additional information

Observed in the Codex desktop app on macOS. Its feedback flow opened this CLI template. Exact elapsed time and reliable reproduction steps are not known.

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 reviewing the uploaded thread 01a08331-7203-7d53-9fc3-e30dd17f9e12 and the usage-meter behavior described there. No repository file, test, model, or reliable reproduction steps are provided; done means identifying whether the displayed allowance was delayed or inaccurate and documenting a verifiable fix or explanation.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.