Codex Now Lets You Save a Rate-Limit Reset for Later
OpenAI is giving Codex users the ability to bank a rate-limit reset and activate it when they actually need it. Go, Plus, Pro and Business users are starting with one free reset.

OpenAI is changing how Codex users can handle occasional rate-limit resets. Instead of receiving extra usage at a time chosen by the company, users can now bank a reset and activate it later - before a large code migration, an intensive development sprint or a task that requires several agents.
The feature began rolling out on June 12, 2026. Users on Go, Plus, Pro and Business plans are starting with one free reset. OpenAI describes this as a gradual rollout, so the option may not appear on every eligible account immediately.
What you need to know
- a banked reset can be activated manually,
- Go, Plus, Pro and Business users receive one free reset,
- an unused reset expires after 30 days,
- the restored usage is available for 7 days after activation,
- Plus and Pro users can temporarily earn more resets through referrals.
How a saved Codex reset works
Codex usage is governed by limits that depend on the user's plan and the work being performed. Long sessions, large repositories and agentic tasks can consume the available allowance much faster than a short coding question.
A saved reset acts as a reserve package of usage. It does not need to be activated as soon as it is issued. A user can wait until the regular limit starts interrupting their work and then restore access from the Codex dashboard.
The distinction matters: OpenAI has not announced a permanent increase to every plan's underlying limits. The new feature provides control over when an additional reset is used.
How to activate the reset
The control is available through the Codex usage dashboard:
- Open the Codex Usage Dashboard.
- Look for the reward badge in the upper-left corner.
- Select the saved reset and confirm activation.
- Check the refreshed usage allowance on the account.
OpenAI says activation may not be reflected immediately. The banked reset expires 30 days after it is issued, while the restored top-up usage expires 7 days after activation.
That means there is little value in triggering the reset merely to test the button. It is more useful to save it for a week in which Codex will be doing substantial work.
More resets through Codex referrals
Until June 24, Plus and Pro users can invite up to three people who have not used Codex before. When an invited user sends their first Codex message, both the referrer and the new user receive another banked reset.
The reward may take some time to appear. OpenAI also requires both accounts to be active and in good standing. A Plus or Pro subscriber can earn up to three additional resets through this promotion.
Business administrators have a separate Codex referral program based on usage credits rather than individual resets. It follows different reward rules and runs until August 1, 2026.
Why this small change is useful
Usage in a conventional chat interface can be relatively predictable. A coding agent behaves differently: one task may finish in a few minutes, while another can inspect many files, run tests, repair failures and continue through several attempts.
Banking a reset reduces the chance that additional capacity arrives during a quiet week and disappears before it is useful. The feature is particularly relevant to developers using Codex on larger repositories or delegating complete workflows instead of isolated code snippets.
Those workflows are becoming more common. OpenAI increasingly presents Codex as a system for multi-step work rather than a question-answering assistant. One example is the tax-preparation agent workflow we covered previously.
What to remember
Saved resets do not answer every question users have about Codex limits, but they add control where the timing was previously decided entirely by OpenAI.
If the feature is already visible on your account, the free reset is best treated as an emergency reserve. It has an expiration date, but activating it too early is not helpful either. The practical choice is to trigger it shortly before a period of intensive Codex use.


