[Windows][Pro 20x] Weekly usage display jumped 60%→97% while reset timestamp changed

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

Exact app version was not captured in the bounded evidence collection yet. The account is using Codex on Windows; I can provide the exact version in a follow-up if needed.

What subscription do you have?

ChatGPT Pro (20x)

What platform is your computer?

Windows 11 Pro x64

What issue are you seeing?

On September 9, 2026, my displayed primary Codex weekly usage changed from 60% used to 97% used, a difference of 37 percentage points (40% remaining → 3% remaining).

Both observations were for limitId=codex with a 10,080-minute (7-day) window.

The later observation is timestamped exactly:

• 2026-09-09 19:03:50.718 Europe/Paris (CEST)
• 2026-09-09 17:03:50.718 UTC
• weekly usage: 97% used
• displayed reset: 2026-09-11 09:49:52 Europe/Paris

The earlier preserved observation shows:

• weekly usage: 60% used
• displayed reset: 2026-09-15 08:12:33 Europe/Paris
• exact timestamp of this earlier observation was not recovered during the bounded evidence search

The important additional anomaly is that the displayed weekly reset date/time also changed, from Sep 15 08:12:33 to Sep 11 09:49:52 Paris time.

Because both the percentage and the reset timestamp changed, I am reporting this conservatively as an unexpected weekly quota-state / reconciliation change. I am not claiming that my Codex workload necessarily consumed 37 percentage points during the interval.

No causal investigation or reproduction experiment was started after noticing the anomaly. Existing work was paused and only bounded collection of already-existing evidence was requested.

What steps can reproduce the bug?

I do not currently have a deterministic reproduction.

Observed sequence:

1. A preserved Codex rate-limit response showed 60% weekly used, limitId=codex, 10,080-minute window, with reset 2026-09-15 08:12:33 Europe/Paris.
2. Existing Codex work was active later on Sep 9. The documented activity near the anomaly was:
   • CT01 Operator: six ticks between 18:42:51 and 18:55:21 Europe/Paris, consisting of reads and review preparation. Model not verified in the preserved evidence.
   • CT02 Navigator: document preparation between 18:38:06 and 18:53:21 Europe/Paris, about 15 minutes. Model not verified in the preserved evidence.
   • CSK4: review transfer refused; no new turn accepted. Model not verified.
   • Correcteur T08: inactive; last admission ended at 18:22:45 Europe/Paris; model verified as gpt-5.6-sol / high.
3. No new candidate, corrector, or run was created during this documented activity. This does not exclude usage elsewhere on the same account.
4. At 2026-09-09 19:03:50.718 Europe/Paris / 17:03:50.718 UTC, the same primary Codex weekly limit was observed at 97% used, with reset 2026-09-11 09:49:52 Europe/Paris.
5. The workload was paused and evidence was preserved rather than attempting to reproduce the event.

The preserved record for the 97% observation is:

ctco_01a08720-37be-71d1-8a9f-39a4cd4e51c7

This identifier is included only as a local evidence reference. I can provide account/session-specific identifiers privately if maintainers need them.

What is the expected behavior?

The weekly usage state and its reset timestamp should be internally consistent and auditable.

If 37 percentage points of allowance were legitimately charged during the relevant interval, there should be enough server-side attribution to identify which product surface, tasks/models, background activity, retries, subagents, or other quota-bearing work produced that change.

If the change instead resulted from a reset event, window re-anchoring, entitlement transition, delayed reconciliation, UI/backend desynchronization, or another account-state change, that event should be visible and explain why both the percentage and reset timestamp changed.

Please reconcile the server-side usage/rate-limit ledger for this account and timestamp range. If the investigation finds incorrectly attributed or incorrectly reconciled usage, please restore the affected allowance.

Additional information

This is a ChatGPT Pro 20x account on Windows.

Cause is currently unknown. No causal investigation has been launched and the workload remains paused.

Potentially related reports / tracker:

• #41220 — Abnormal Codex usage/quota depletion and usage-accounting inconsistencies — cross-report tracker
• #42660 — Weekly Codex quota reset/reconciliation appears broken — quota exhausted with no local activity
• #21216 — Weekly usage % jumps when rate-limit/account state changes
• #44201 — Weekly reset timestamp appears stale after recent global reset

I am deliberately not attributing this to any specific task or model without server-side reconciliation. The key verified facts are the 60% → 97% displayed weekly usage change and the simultaneous Sep 15 → Sep 11 displayed reset-time change on the same 7-day Codex limit.

No source file, test, or entry point is named. Start by reviewing the related issues (#41220, #42660, #21216, and #44201) and reconciling the server-side rate-limit ledger for the supplied timestamps and evidence reference; done means the 60%→97% change and reset-time shift are explained or the affected allowance is restored.