Weekly Limit Increased to 100% Without Any Usage

Resolved 💬 2 comments Opened May 5, 2026 by lewiskimaru Closed May 5, 2026

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

Version 26.429.30905 (2345)

What subscription do you have?

Plus (10x promotional period)

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Bug Report: Weekly Limit Increased to 100% Without Any Usage

Subscription: Plus (10x promotional period)
Platform: Codex
Date of occurrence: May 4–5, 2026

What happened

On the morning of May 4, 2026, my weekly usage was at 70% with a renewal date showing May 7. I did not use Codex at all for the next 2 days. On May 5 evening, I returned to find my weekly usage was now at 100% with a new renewal date of May 12. No tasks were initiated, no agents were running, and no sessions were open during that 2-day period.

What steps can reproduce the bug?

Steps to reproduce

  1. Use Codex on the Plus plan until weekly usage reaches a partial percentage (e.g. 70%)
  2. Note the renewal date shown in the usage panel
  3. Stop using Codex completely for 2 or more days — do not initiate any tasks or open any sessions
  4. Return and check the weekly usage panel
  5. Observe whether the usage percentage and renewal date have changed without any user-initiated activity

What is the expected behavior?

Expected behavior

Weekly usage should remain at 70% with a renewal date of May 7, unchanged, since no usage occurred between May 4 and May 5.

Actual behavior

Weekly usage jumped from 70% to 100% with the renewal date shifting from May 7 to May 12, despite zero usage during that period.

Impact

The 30% remaining quota I had not yet used was not available upon return. Whether this is a metering bug, an unannounced system reset, or a display issue is unclear — but the end result is that paid quota appeared to disappear without corresponding usage.

Please investigate what caused the usage and renewal date to change during a period of zero activity.

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗