IssueRaiser

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

ux (Sysadmin)

[Codex Desktop][Windows] Weekly quota jumped 67 points in 38 seconds (Oct 16, 2026; 18:10 UTC)

EgorStepkinOct 16, 2026, 7:02 PM

## Summary **New evidence from local Codex logs:** On **October 16, 2026**, the *remaining WEEKLY Codex allowance* dropped from **77% at 21:10:43 to 10% at 21:11:21 Moscow time (UTC+3)** — **67 percentage points in 38 seconds**. According to a Codex-assisted inspection of local logs, token counters rose by only **380,821 tokens** between these two records, including **373,120 cached-input tokens** (~98% of the increment). The weekly reset timestamp did not change. This is a significant **unexplained quota-meter discontinuity**. It does *not* by itself prove that the backend billed those 380,821 tokens incorrectly: delayed posting of previous requests, usage outside the inspected local sessions, weighting, and reconciliation must all be checked against server-side records. The underlying raw log excerpts have not yet been attached to this public issue. My remaining weekly quota later reached **6%**, leaving development effectively blocked. This concerns the **weekly** allowance, not a five-hour window. ## Revised timeline The initial report relied on the times when the drop was noticed in the UI. The following **more precise local-log timestamps supersede the initial inferred 21:16 start time**. | Oct 16, Moscow time (UTC+3) | Weekly allowance remaining | Evidence | |---|---:|---| | 20:14 | 79% | Local Codex log summary | | **21:10:43** | **77%** | Local Codex log summary | | **21:11:21** | **10%** | Local Codex log summary — 67-point drop in 38 s | | ~21:26 | 8% | Initi

Comments (0)

No comments yet. Start the discussion.

Comment on this issue