openai / openai/codex

CLI weekly allowance refills unexpectedly and repeatedly postpones the reset date

Open
#38,901 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI rate-limits
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

codex-cli 0.147.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.6-sol with reasoning set to High and Fast mode enabled

What platform is your computer?

Windows with Codex CLI running under WSL/Linux. Exact uname -mprs output was not recorded.

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

Windows Terminal with WSL. Exact terminal version was not recorded.

Codex doctor report
not available / not run
What issue are you seeing?

My weekly usage allowance has been refilled unexpectedly while substantial allowance was still available, and each refill appears to move the displayed reset date farther into the future.

Observed timeline (Europe/London):

  1. The meter showed 97% remaining and said it would reset on 14 Aug 2026.
  2. After I had used only about 3%, the allowance unexpectedly returned to 100%, but the reset date moved to 16 Aug.
  3. About three days before 16 Aug, I coded for roughly one hour. The displayed reset date then moved to 19 Aug.
  4. On 16 Aug, /status showed:
OpenAI Codex (v0.147.0)
Model: gpt-5.6-sol (reasoning high, summaries auto)
Account: ChatGPT Plus
Weekly limit: 99% left (resets 01:49 on 21 Aug)
Credits: 2500 credits

The displayed date therefore moved 14 Aug → 16 Aug → 19 Aug → 21 Aug, rather than remaining fixed at the date originally presented to me.

The additional allowance is welcome. The problem is that an unsolicited refill appears to replace the active weekly window and postpone its renewal date. This makes the quota difficult to plan around: I would rather use the remaining allowance until the promised date and receive the normal renewal then.

This report concerns the weekly usage allowance. The per-session context-window percentage is a separate indicator.

What steps can reproduce the bug?

I cannot trigger the apparent server-side refill deterministically. This is the observed sequence:

  1. Use Codex CLI on a ChatGPT Plus weekly usage window.
  2. Record the percentage remaining and displayed reset date.
  3. Continue using Codex normally without manually redeeming a reset.
  4. Observe the weekly allowance unexpectedly increase to or near 100%.
  5. Observe the displayed reset date move several days later.
  6. Continue normal usage and observe the reset date move later again.

No error message was shown and I did not manually request these refills.

What is the expected behavior?

The displayed weekly reset date should remain stable for the active usage window.

If OpenAI grants additional allowance before that date, it should preferably:

  • be added without postponing the active reset date; or
  • be banked as an optional reset that the user can redeem later.

At minimum, Codex should explain why the balance changed, whether unused allowance was preserved, and why the reset date moved. A reset-event history showing the previous and new balance and reset timestamps would make the behavior auditable.

Additional information

This appears closely related to #38332, but this report documents a separate account timeline in which the reset date moved repeatedly through 14, 16, 19, and 21 Aug.

This issue supersedes #38900, which was not submitted using the dedicated CLI issue-form structure.

My account email, local directory, and session ID have been omitted from this public report. Account-specific telemetry can be provided privately if requested.

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 with the CLI /status output and the weekly allowance/reset handling, using the reported 14, 16, 19, and 21 Aug timeline as the failure case. Compare the behavior with related issue #38332 and determine whether the reset date can move after an unsolicited refill; done means the active reset remains stable or the CLI clearly explains the refill and new date.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.