openai / openai/codex

Banked usage reset was consumed but weekly allowance remained at 7% for hours

Open
#41,459 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 the Codex App are you using (From “About Codex” dialog)?

26.825.32147 (build 7303)

What subscription do you have?

ChatGPT subscription (exact tier not provided)

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

I explicitly redeemed one available banked Codex usage reset on August 28, 2026. The reset was consumed, but several hours later the weekly usage meter still shows only 7% remaining. The weekly allowance did not reset.

Feedback/diagnostic ID: no-active-thread-01a04b94-4ee1-7e83-b9c4-44bbc37b64fd

This appears to be a backend usage-accounting or reset-persistence failure rather than a short UI refresh delay because the state remained unchanged for hours.

What steps can reproduce the bug?
  1. Have a banked Codex usage reset available while the weekly allowance is nearly exhausted.
  2. In the Codex desktop app, redeem the banked reset once.
  3. Confirm that the reset credit is consumed.
  4. Refresh or revisit usage after several hours.
  5. Observe that weekly usage still reports 7% remaining instead of a restored allowance.

No second reset redemption was attempted.

What is the expected behavior?

Redeeming a banked reset should promptly restore the eligible weekly Codex allowance and the usage meter should reflect the restored balance. If the reset cannot be applied, the banked reset should not be consumed.

Additional information

Observed on August 28, 2026.

This is similar to #31532 and #34865, but is a fresh occurrence on Codex App 26.825.32147 with a new diagnostic ID that should allow the affected backend event to be traced.

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 tracing diagnostic ID no-active-thread-01a04b94-4ee1-7e83-b9c4-44bbc37b64fd and compare this report with related issues #31532 and #34865. Done means redeeming a banked reset restores the weekly allowance and meter promptly, or leaves the reset unconsumed when restoration fails.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.