Bank scheduled weekly resets instead of discarding remaining Codex usage

Open 💬 2 comments Opened Aug 3, 2026 by Kelsiito
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

Codex currently resets the weekly usage window on a fixed schedule, even when the user still has included weekly usage remaining. Any remaining allowance is effectively discarded when the scheduled reset occurs.

I propose banking the scheduled weekly reset instead of immediately replacing the user's remaining allowance.

Proposed behaviour

When the weekly reset time is reached:

  • If the current weekly allowance has already been exhausted, reset it normally.
  • If weekly allowance remains, keep that remaining allowance active.
  • Store the scheduled weekly reset as a banked weekly reset.
  • When the active weekly allowance is exhausted, automatically apply the oldest banked weekly reset, or allow the user to apply it manually.
  • Each stored reset should represent one new full weekly allowance.

Example:

  1. A user reaches the weekly reset date with 30% allowance remaining.
  2. The 30% remains available instead of being discarded.
  3. The scheduled weekly reset is banked.
  4. Once the remaining 30% is consumed, the user applies the banked reset and receives a new full weekly allowance.

Accumulation and safeguards

The maximum number of banked weekly resets and their expiration policy can be determined by the OpenAI team based on capacity, abuse prevention, and plan economics.

Suggested safeguards:

  • Consume the oldest reset first.
  • Keep weekly resets separate from the independent five-hour rate-limit window.
  • Do not allow resets to be transferred or converted into API or monetary credits.

Why this would be useful

This would not grant users more included usage than their plan already provides. It would prevent users from losing included usage simply because their workload is not distributed evenly across fixed weekly windows.

This is particularly useful for project-based development, where usage may be low during some weeks and intensive during others.

Implementation note

Codex already has client-side support for listing and consuming banked rate-limit reset credits. The main change appears to require backend entitlement logic that converts a scheduled weekly reset into a banked weekly-reset credit whenever the current weekly allowance has not yet been exhausted.

A weekly-specific reset type may also be needed so redeeming it does not reset the independent five-hour limit.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 25 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #36436

Powered by Codex Action

pvdecode · 23 days ago

this would be very useful.