›_ Codex Issues
Codex Issues / #38900

Weekly usage allowance refills unexpectedly and repeatedly postpones the displayed reset date

Resolved 💬 4 comments Opened Aug 16, 2026 by ElenaViewSynthesis Closed Aug 16, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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?

Codex CLI under WSL/Linux on Windows.

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 reset date has therefore moved from 14 Aug → 16 Aug → 19 Aug → 21 Aug, rather than remaining fixed at the date originally presented to me.

The extra allowance is welcome, but the current behavior makes the weekly limit unpredictable. When the UI promises a reset in a certain number of days, I plan my work around exhausting the available allowance by that date. An unsolicited refill should not silently replace the active window and postpone the promised renewal date.

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, but this is the observed sequence:

  1. Use Codex CLI on a ChatGPT Plus weekly window.
  2. Note 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. Repeat normal usage and observe the reset date move later again.

What is the expected behavior?

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

If OpenAI grants extra 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, the UI should explain why the allowance changed, whether unused allowance was preserved, and why the reset date moved. A reset-event history would also make the behavior auditable.

I would prefer to use the entire remaining allowance until the originally displayed date and receive the normal renewal then, rather than receive an unsolicited refill that repeatedly pushes the reset date forward.

Additional information

This appears closely related to #38332, but I am reporting a separate account timeline in which the displayed date moved multiple times through 14, 16, 19, and 21 Aug.

I have omitted my account email, local directory, and session ID from this public report. I can provide account-specific telemetry privately if requested.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 11 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #38332
  • #38789
  • #37776

Powered by Codex Action

ElenaViewSynthesis · 11 days ago

Superseded by #38901, which was submitted using the dedicated Codex CLI issue-form structure.

ElenaViewSynthesis · 11 days ago

@jif-oai @anp-oai @etraut-openai @bolinfest @pakrym-oai @charliemarsh-oai @owenlin0 @felixxia-oai @sayan-oai @fcoury-oai — tagging for maintainer visibility because the repository's own duplicate-detection bot identified a recurring cluster of closely related reports: #38332, #38789, and #37776. The replacement report, #38901, was also linked to the same cluster.

These reports span multiple users and dates (at least 10–16 Aug), both Plus and Pro subscriptions, and Codex App/CLI surfaces. The shared symptom is that an unsolicited early refill returns the weekly allowance to or near 100% while moving the displayed reset date later, apparently superseding unused allowance from the active window.

That recurrence strongly suggests this is a persistent quota/reset-window issue rather than an isolated local-client event, although a service-side cause is an inference until OpenAI confirms it. Could the team please consolidate and acknowledge the cluster and clarify:

  • whether an early refill overwrites the unused balance and re-anchors the seven-day window;
  • whether the originally promised reset remains banked or is lost; and
  • whether a stable reset date or visible reset-event history can be provided?

For clarity, #38900 was closed only because it was superseded by the correctly structured CLI report #38901, not because the underlying behavior was resolved.

ElenaViewSynthesis · 11 days ago

One implementation path worth checking is weekly_reset_at (or quota_window_started_at). A possible failure mode is that an unsolicited early refill recalculates the reset as weekly_reset_at = refill_timestamp + 7 days, re-anchoring the weekly window even though the user has not reached the usage limit. This would explain why the displayed reset date keeps moving farther back whenever the allowance refills early. This is a hypothesis rather than a confirmed root cause.