codex - 💡(How to fix) Fix Codex weekly usage meter switches to inconsistent reset window

Summary

Codex Desktop appears to switch the weekly subscription usage meter between inconsistent secondary rate-limit windows. In one local session log, the weekly bucket was 27% used with a reset on May 23. Roughly two hours later, a fresh thread reported the same secondary.window_minutes: 10080 bucket as 99% used with a reset on May 18. The reset timestamp moved backward by about five days.

This surfaced in the UI as weekly Codex usage jumping from about 75% remaining to about 1% remaining shortly after the user believed the subscription usage had recently reset.

Environment

• Product: Codex Desktop
• Originator in log: Codex Desktop
• CLI version in log: 0.131.0-alpha.9
• Plan type in rate-limit payload: pro
• Local timezone: America/Los_Angeles
• Date observed: May 17, 2026

Evidence from local session logs

Earlier same day:

{
  "timestamp": "2026-05-17T18:25:31.464Z",
  "rate_limits": {
    "limit_id": "codex",
    "secondary": {
      "used_percent": 27.0,
      "window_minutes": 10080,
      "resets_at": 1779571027
    },
    "plan_type": "pro"
  }
}

1779571027 corresponds to May 23, 2026 14:17:07 local time.

Later same day, in a fresh projectless thread:

{
  "timestamp": "2026-05-17T20:20:06.727Z",
  "rate_limits": {
    "limit_id": "codex",
    "secondary": {
      "used_percent": 99.0,
      "window_minutes": 10080,
      "resets_at": 1779144603
    },
    "plan_type": "pro"
  }
}

1779144603 corresponds to May 18, 2026 15:50:03 local time.

Why this looks wrong

Both payloads report secondary.window_minutes: 10080, which appears to be the weekly Codex usage window. But the reset timestamp moved backward from May 23 to May 18. If this is a single weekly subscription usage bucket, that should not happen.

Possible explanations:

• The UI/backend is switching between different quota buckets while labeling both as weekly usage.
• One of the resets_at timestamps is wrong.
• A new thread is being attached to an older near-expired quota bucket.
• secondary is not actually the subscription weekly allowance, but the UI presents it as such.

Relevant local log paths

Redacted local paths on the affected machine:

• ~/.codex/sessions/2026/05/17/rollout-2026-05-17T11-25-29-019e372f-a50a-7441-aa1b-87243bedfcd9.jsonl
• ~/.codex/sessions/2026/05/17/rollout-2026-05-17T13-19-53-019e3798-5ea5-7b01-bf43-d26b50270cbd.jsonl

I can provide more surrounding log excerpts if helpful.