Understand Codex resets and a changed refresh date

Distinguish scheduled, banked, automatic and purchased Codex resets. Understand changed refresh dates without confusing public posts with your account.

For understanding subscription allowances and refresh dates. Product rules were checked on October 23, 2026. Examples use fictional observations; the copied prompt only explains information you provide.

Start here

Identify the reset type and affected allowance before interpreting a date. Public announcements, banked-reset activity and personal usage readings answer different questions.

1. Name the kind of change

The word reset can describe several different events. Start with the evidence you actually have, rather than treating every reset as the same benefit.

What you sawMeaningWhat it does not establish
Scheduled refreshA regular allowance window reaches its refresh time.A public reset announcement or extra credit.
Banked reset receivedA reset was stored for later use.That your allowance was already refreshed.
Banked reset usedEligible covered allowances were restored.That an allowance already at 100% restarted.
Automatic or global resetAn offer applies directly to selected accounts and limits.That every account or every allowance was included.
Purchased instant resetAn eligible paid reset applies immediately.A saved reset for later or additional usage credits.
Usage creditsA separate pay-as-you-go usage balance.A refreshed subscription allowance or banked reset.

Reference: OpenAI: How resets work in Codex · OpenAI: Paid weekly Work and Codex rate limit resets · OpenAI: Using Codex with your ChatGPT plan

2. Understand why the date can move

A reset can replace the schedule for the allowance it restarts. This does not change your subscription billing date. A changed date alone does not prove another banked reset was spent.

For a purchased instant reset, OpenAI describes the new weekly period as starting with the first Work or Codex request afterward. Its next weekly refresh is seven days after that request, which can differ from the payment time.

Read the affected allowance and its displayed time together. A time calculated from a public post or purchase is not a verified account reading.

Reference: OpenAI: How resets work in Codex · OpenAI: Paid weekly Work and Codex rate limit resets · OpenAI: Using Codex with your ChatGPT plan

3. Compare three fictional cases

These examples show how to reason from limited evidence. They are not measurements of your account or promises about a future reset.

ObservationSupported conclusionStill unknown
History shows Reset received at 09:00 UTC.A banked reset arrived for later use.Whether or when any allowance refreshed.
Weekly is 100%, short-window allowance is 10%; a banked reset is then used.The short-window allowance can be restored while the already-full weekly allowance is not restarted.A new timestamp without a displayed reading.
Instant reset purchased Monday; first later request Tuesday at 14:00 UTC.The documented weekly scheduling interpretation is the following Tuesday at 14:00 UTC.Actual application and the account-displayed result.

Reference: OpenAI: How resets work in Codex · OpenAI: Paid weekly Work and Codex rate limit resets

4. Keep missing evidence visible

Banked history distinguishes received from used; paid and automatic resets are absent from that history. A missing entry therefore cannot identify which event occurred.

If a request remains blocked, distinguish the exhausted allowance from context length, account access or another error. Codex usage can depend on the task, model and context; a percentage is not a fixed count of equally sized requests.

A useful explanation keeps three columns: supported observations, remaining unknowns and one safe next check. It should never invent a delivery time or spend a second reset merely to diagnose the first.

Reference: OpenAI: How resets work in Codex · OpenAI: Using Codex with your ChatGPT plan

5. Use public history for the right question

The Codex Reset Tracker is a companion for public events and timing references. It cannot inspect your subscription allowance. Keep an announcement, a reported action and an observed account change separate.

For your personal schedule, the account-displayed allowance and reset time take precedence over an unofficial countdown. The prompt below helps interpret redacted notes without taking account actions.

Reference: OpenAI: Using Codex with your ChatGPT plan · Codex Pets: Codex Reset Tracker

Explain redacted reset observations

Help me understand a Codex reset using only redacted observations I provide. Separate a scheduled allowance refresh, a received or used banked reset, an automatic/global reset, a purchased instant reset and usage credits. Identify the affected allowance and any displayed time/timezone; list missing evidence as unknown. Distinguish a public announcement, an observed account change and a confirmed redemption or payment. Separate restored allowance from a verified new refresh time; percentages alone do not supply a new timestamp. Explain a changed date only as far as the evidence supports. Use this guide's dated source distinctions; verify current official documentation if available and label any unverified current claim. Do not read my account, change settings, redeem a reset, buy anything or perform other actions. Return: What the observations support; What remains unknown; One safe next check that spends nothing.

My redacted observations: [paste observations, without account identifiers, receipts, tokens or private messages]

Read the prompt before sending it. Copying does not run it.

Check your result

  • Name the reset type supported by the observations, or leave it unknown.
  • Identify which allowance changed and retain any supplied timezone.
  • Keep received, redeemed, paid and observed application distinct.
  • Separate documented scheduling behavior from a verified account timestamp.
  • Finish with one check that uses no reset, purchase or account change.

Sources and scope

Official references support the product behavior described above. The task prompts and practical checks are our community guidance.

Something changed in your version? Send a correction with the guide URL, platform, and version. Leave out credentials and private project content.

Put it into practiceChoose your next guide

Analytics preferences

Google Analytics measures visits and actions. Microsoft Clarity records page interactions to help us improve navigation. These services can receive device information, page URLs and identifiers, and use cookies. Tool inputs are masked from Clarity.

Reject analytics to stop loading both services. Your choice applies to this browser for 180 days. You can change it here at any time. Read our privacy policy.

Loading your preferences…