Codex rate-limit bug: banked reset consumed, 94% weekly quota dropped to 0%

What version of the Codex App are you using (From “About Codex” dialog)?

26.903.8094.0 Codex CLI：0.154.0-alpha.3

What subscription do you have?

ChatGPT Pro20X

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Hi, I’d like to report a suspected incorrectly applied banked Codex reset and request an account-level investigation.

I used my banked reset today, September 10, 2026 (China Standard Time, UTC+8). At the time, my weekly usage page was still showing approximately 94% allowance/usage status.

After I consumed the banked reset, my Usage page subsequently changed unexpectedly: my weekly usage window was recalculated/reset, and my scheduled weekly reset date changed from September 16 to September 12.

However, the banked reset I had just used was still marked as consumed and was not restored.

This appears to be a usage-window/reset-accounting inconsistency rather than a request for a courtesy reset. The banked reset was consumed immediately before the system recalculated my weekly allowance and reset schedule, so the benefit associated with that banked reset appears to have been lost or overridden by the later system-side recalculation.

Could you please review the account logs for:

• the exact time my banked reset was consumed;
• my weekly usage before and after the reset;
• the change of my weekly reset date from September 16 to September 12;
• any automatic/global/account-level reset or usage-window recalculation that occurred afterward;
• whether the consumed banked reset should be restored because its effect was superseded by that system-side change.

I can provide screenshots of my current Usage page and any earlier screenshots showing the previous September 15 reset date.

I am specifically requesting an investigation of a suspected incorrectly applied banked reset, not a courtesy reset.

Thank you.

What steps can reproduce the bug?

Feedback ID: 01a0201d-630a-7c31-8a9e-3d57c7a88f42

What is the expected behavior?

No response

Additional information

No response

Start with Feedback ID 01a0201d-630a-7c31-8a9e-3d57c7a88f42 and the account usage/reset logs. Compare the banked-reset consumption with weekly usage, the reset-date change from September 16 to September 12, and any subsequent recalculation; done means determining whether the reset was incorrectly consumed and documenting the resulting account action.