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):
- The meter showed 97% remaining and said it would reset on 14 Aug 2026.
- After I had used only about 3%, the allowance unexpectedly returned to 100%, but the reset date moved to 16 Aug.
- About three days before 16 Aug, I coded for roughly one hour. The displayed reset date then moved to 19 Aug.
- 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:
- Use Codex CLI on a ChatGPT Plus weekly window.
- Note the percentage remaining and displayed reset date.
- Continue using Codex normally without manually redeeming a reset.
- Observe the weekly allowance unexpectedly increase to or near 100%.
- Observe the displayed reset date move several days later.
- 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.
What version of Codex CLI is running?
codex-cli 0.147.0What subscription do you have?
ChatGPT Plus
Which model were you using?
gpt-5.6-solwith 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):
/statusshowed: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:
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:
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.