whenreset.news
Codex · Usage guides

Codex Reset Time: 5-Hour vs Weekly Limits

Why did your Codex five-hour allowance reset but not your weekly limit? Learn how to check /status, avoid limit traps, and track your actual Codex reset time.

Reviewed 5 min read5 sources
Codex

The quick answer

Five-hour windows and weekly limits are separate constraints: waiting for the earlier Codex reset time does not mean your entire allowance has refreshed. OpenAI's pricing and usage guidance outlines both five-hour usage and potential weekly limits; local CLI work and cloud environments share this plan allowance. Use your account dashboard for your personal reset times.

ChatGPT Work and Codex share usage, credits and limits, so also check work done in ChatGPT Work on the same account when investigating unexpected consumption.

Choose your next step

  1. Only the five-hour window is empty: use its displayed reset time; check the weekly balance separately.
  2. The weekly window is also empty: the earlier five-hour reset will not clear that restriction. Record both times.
  3. No reset time is shown: check the usage dashboard or /status; leave the time unknown instead of adding five hours yourself.

Find the window blocking your task before expecting a reset

Suppose your dashboard indicates 0% remaining in the five-hour window with a reset scheduled today at 16:00, alongside 30% remaining in the weekly limit resetting on Friday. Today at 16:00 is your immediate checkpoint for a five-hour Codex reset. If both windows show 0%, reaching 16:00 alone will not clear the weekly restriction.

A common point of confusion is observing a fully replenished five-hour progress bar right beside an exhausted weekly bar. Do not blend these percentages or attempt to derive one from the other. Track each window with three data points: window name, remaining allowance, and next reset timestamp, including the full date and time zone.

Check available limits and confirm the reset time

Open your Codex usage dashboard and inspect the windows shown for your account. In supported clients, /status shows available context and rate-limit information. Use the official dashboard for the reset time; if your client also shows a recovery time, check it against the same account and window. Context usage is not your remaining plan allowance. See the desktop command reference or CLI command reference for your client.

Always plan around the dashboard's explicit reset timestamp rather than manually adding five hours to when you started coding. Do not use Monday midnight or billing renewal as a default reset time. Record an unavailable timestamp as unknown rather than assuming a default.

If the web dashboard and terminal report conflicting data, inspect your workspace menu and run codex login status to verify authentication. OpenAI distinguishes subscription sign-ins from API-key authentication; API usage is billed by consumption rather than subscription quotas.

How a public Codex reset announcement relates to your account

Public records can have different types and scopes. Your personal window records the reset time displayed for your account. Always read an announcement's scope and official source before checking its impact on your account.

A notice targeting an enterprise tier does not automatically apply to individual subscriptions. Similarly, an announcement regarding reset credits does not mean every user's weekly allowance has refreshed. Historical intervals provide helpful context, but your account dashboard remains the source of truth for your Codex reset time.

Billing renewal, reset credits and actual recovery

A billing renewal date is not a substitute for the reset timestamp of a five-hour or weekly window. Keep the invoice cycle and the usage windows separate.

A banked reset is an entitlement you may be able to redeem, not evidence that it has already run. Check the current offer or account dialog for eligibility and expiry; historical referral offers do not establish today's terms. After redeeming an available reset, refresh the official dashboard and verify which window changed. The pricing page distinguishes banked reset rewards from additional paid credits.

Verify the window after the time arrives

Record the full date and time zone if you use the personal timer on the Codex page. At expiry, refresh the official usage dashboard, confirm remaining allowance in the blocking window and then try a small necessary next step. The timer does not query or restore OpenAI allowance.

If the reset did not unblock the task, return to limit troubleshooting. If you want to understand rapid consumption, see how Codex usage works.

What does Codex token reset time mean?

If you mean when you can use Codex again, check the account allowance and its displayed reset time. If you mean making room in a long conversation, that is context management. A context percentage does not tell you when account usage will reset.

In the CLI, /new starts a fresh chat, /clear starts a fresh chat and clears the terminal view, and /compact summarizes earlier turns to free context while retaining important details. These are conversation operations; do not treat them as ways to replenish account allowance. Official CLI commands

How to redeem an available Codex reset

Having a banked reset and having paid credits are different. To use an earned reset in a supported CLI:

  1. Check your account for an available reset, its eligibility and expiry. Do not assume an old invitation offer still applies.
  2. With Codex service account authentication, open /usage and select the option to redeem an available earned reset. The command does not grant a reset to every account.
  3. Refresh the official usage dashboard. Check every displayed window’s name, remaining allowance and reset timestamp, including the date and time zone.

Confirm which limits changed before continuing. The CLI reference documents the redemption menu; purchasing extra credits is a separate continuation route.