Summary
My Codex usage limit is described/understood as a weekly limit, but the reset window shown in the Codex UI appears to be 10 days for the current cycle. This effectively reduces the usable quota for the following week and doesn’t match either a calendar-week reset or a rolling 7×24h reset.
What I’m seeing
- Week 2 (as shown/previously experienced): Dec 6 → Dec 14
- I used Codex on Dec 14 and Dec 15 (and have usage shown across these days).
- Expected Week 3: Dec 14 → Dec 21 (7 days)
- Actual Week 3 (currently shown): Dec 14 → Dec 24 (10 days)
- The UI also shows a reset timestamp like “Resets Dec 25, 2025 10:21 PM” (screenshot attached).
Why this seems wrong
“Your Codex weekly usage limit resets every 7 days from the moment you first use it…”
But if the new window begins on Dec 14, a rolling 7-day reset should land around Dec 21, not Dec 24/25. If it’s calendar-based, it should also not drift like this. Either way, the displayed window looks longer than a week.
Steps to reproduce (what I did)
- Use Codex normally across consecutive days (in my case, Dec 14–Dec 18, including Dec 14/15).
- Go to Codex → Settings → Usage.
- Observe the reset date/time and the implied window for the current “weekly” period.
Expected behavior
- A “weekly limit” should reset on a predictable schedule:
- Either fixed calendar weeks, or
- A rolling 7×24 hour period from the start of the cycle,
- …but not a window that expands to ~10 days and reduces the next cycle’s usable time/quota.
Actual behavior
- The Codex UI indicates my current “weekly” cycle runs Dec 14 → Dec 24 (with reset shown as Dec 25 ~10:21 PM).
Impact
- This effectively shrinks the next week’s available usage (or shifts it forward) despite consistent daily usage.
- It also makes it hard to plan usage if the “weekly” boundary can stretch beyond 7 days.
Questions for the team
- What is the authoritative definition of a Codex “weekly” limit? (Calendar week vs rolling 7 days vs something else)
- If it’s rolling: why is the reset not 7 days after the start of the period (Dec 14)?
- Is this a known UI bug vs backend accounting issue?
- Can support/devs check my account for the specific reset logic being applied?
