Feature request: let available weekly resets bypass the 5-hour usage window

Open 💬 1 comment Opened Jun 18, 2026 by Yemvis

Feature request

When a user has a weekly usage reset available, Codex should not block them on the shorter 5-hour usage window, or should provide an explicit "use reset now / intensive mode" action that lets them continue immediately.

Current behavior

The Codex usage UI can show separate quota concepts at the same time, for example:

  • 5-hour usage window with a reset time later today
  • weekly usage window with a later weekly reset date
  • 1 reset available

The reset appears to apply to the weekly usage bucket, not the 5-hour bucket. This creates a confusing situation: the account may have an available weekly reset, but the user can still be blocked or throttled by the shorter 5-hour window.

Problem

If a reset is available, the user has already been given an explicit extra recovery/continuation mechanism. But the 5-hour window can still interrupt active work before that reset is useful.

From the user's point of view:

I have a reset available, so I am willing to spend it to continue an intensive work session now. Why am I still forced to wait for the 5-hour window?

This is especially painful for agentic coding sessions, where stopping for several hours can break flow, leave work half-finished, or force the user to resume later with less context.

Desired behavior

Codex should support one of these behaviors:

  1. If reset_available > 0, do not hard-block on the 5-hour window. Treat the available reset as permission to continue an intensive session.
  2. Add an explicit action such as Use reset now, Start intensive session, or Bypass 5-hour window using reset.
  3. If bypassing automatically is not desirable, show a clear prompt when the 5-hour window is exhausted:

``text
You have 1 weekly reset available. Use it now to continue without waiting for the 5-hour window?
``

Important distinction

This request is not asking for unlimited usage.

The requested behavior is specifically:

  • keep the weekly reset as the scarce resource;
  • let the user choose to spend that reset when active work is blocked by the short 5-hour window;
  • make the relationship between 5h, weekly, and reset available understandable.

Why this matters

Power users sometimes need a short burst of heavy Codex usage to finish a task. If the account shows an available reset, it should be possible to convert that into immediate continuity instead of waiting for the 5-hour timer.

This would make the usage UI feel more coherent:

  • 5h = normal short-window pacing
  • weekly = larger plan budget
  • reset available = intentional override / intensive-session recovery

Suggested UI copy

Possible button or menu item:

Use reset to continue now

Possible explanation:

This will spend one available weekly reset and allow Codex usage to continue without waiting for the current 5-hour window to refresh.

Related but distinct issues

There are existing issues about incorrect usage accounting, stale status, and missing usage visibility. This request is narrower: it asks for product behavior that lets an available weekly reset intentionally override the short 5-hour window.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗