Banked Codex usage reset was consumed/disappeared while Codex was inactive

What issue are you seeing?

Uploaded thread ID: 019fcc55-0f4b-7c21-9b44-69c3ee54dc8e

A banked Codex usage reset disappeared from my account even though I did not intentionally redeem it.

On August 13 at 02:17 UTC, my weekly Codex usage was only 27% used (73% remaining), and the normal weekly reset was scheduled for August 18.

I then stopped using Codex and went to sleep.

I audited the entire period from 02:17:01 UTC to 06:04:17 UTC and found zero local Codex activity:

• 0 model/reasoning/tool/task/token-count events across all local Codex session JSONL files
• 0 rows in Codex logs_2.sqlite during that period, despite the database covering August 8–17
• no Codex/OpenAI activity in journalctl
• no Codex-related systemd services, timers, cron jobs, at jobs, or alternate active CODEX_HOME
• an old backup Codex environment was also checked and had been inactive since May

At 06:04:17 UTC I used Codex again for the first time.

The first quota snapshot at 06:04:28 UTC suddenly showed:

• weekly usage: 0% used
• next weekly reset: approximately August 20 at 06:04 UTC

So the observable account state changed from:

27% used / reset scheduled for Aug 18

to:

0% used / reset scheduled for Aug 20

while the local Codex installation was completely inactive.

From that point onward the newly anchored weekly window behaved normally and increased from 0% to 100%.

This pattern looks consistent with a full banked reset being applied and the weekly window being re-anchored by approximately 7 days.

The problem is that I did not redeem that reset, and there was no reason for me to do so with 73% of my weekly allowance still remaining.

I also searched the available local logs for account/rateLimitResetCredit/consume and found no corresponding local redemption event.

The banked reset subsequently disappeared and Codex reports: "No usage limit resets available."

OpenAI Support asked me to submit /feedback from the affected session and report the issue here.

Please investigate what caused the banked reset to be consumed, invalidated, or otherwise removed without an intentional redemption.

What steps can reproduce the bug?

I cannot reliably reproduce this because the reset appears to have been consumed or removed spontaneously at the account/backend level.

Observed sequence:

1. Have a banked Codex usage reset available.
2. Weekly usage was 27% used, with the normal weekly reset scheduled for Aug 18.
3. Stop using Codex completely.
4. No local Codex activity occurred for approximately 3 hours 47 minutes.
5. Start using Codex again.
6. The first subsequent quota snapshot shows weekly usage reset to 0% and the weekly reset date moved to approximately 7 days later (Aug 20).
7. The banked reset is no longer available.

Affected uploaded thread:
019fcc55-0f4b-7c21-9b44-69c3ee54dc8e

What is the expected behavior?

No response

Additional information

No response

Start with the uploaded thread and the reported quota snapshots, then review the local Codex session JSONL files and logs_2.sqlite evidence from the affected period. The issue provides no named code entry point or reliable reproduction; done means identifying why the banked reset disappeared without local activity and documenting or correcting the account-side behavior.