Codex Reset: Banked vs Automatic vs Paid, and When to Use Each
TL;DR
Codex has three kinds of usage reset - banked, automatic and paid - and they move your weekly refresh date in different ways. What OpenAI documents, the 80% rule, and what to do Monday.
Last updated: October 23, 2026
"Codex reset" now means three different things, and they do not behave the same way. OpenAI's help center splits them into banked resets you save, automatic (sometimes called global) resets it applies to you, and purchased instant resets. The detail that bites people is the same in all three: a reset restarts the usage period, so your next weekly refresh date moves.
This is the follow-up to our Codex usage limits and pricing guide, which covers what each plan buys. Here the question is narrower: which reset do you have, when does it help, and when does it cost you.
What OpenAI documents#
Everything below comes from two OpenAI help articles: How resets work in Codex and Paid weekly Work and Codex rate limit resets. Both showed as recently updated when we read them on October 23, 2026, so the rules are moving; re-read them before you plan around a specific date.
| Type | Who gets it | Saved for later | Counts in History |
|---|---|---|---|
| Banked reset | Granted by OpenAI, including referral promotions | Yes, until it expires | Yes (received and used) |
| Automatic / global reset | Accounts and limits chosen for an offer | No - applied directly | No |
| Purchased instant reset | Selected Plus and Pro personal accounts | No - applies immediately | No (receipt in billing) |
OpenAI describes free banked and automatic resets as discretionary promotional benefits with no guaranteed availability or schedule, and says none of the three permanently raise your plan's limits or add credits.
What a full reset restores#
A full banked reset restores the main Codex allowances on your current plan, per OpenAI:
- Go: the monthly allowance.
- Plus and Business Standard: the 5-hour and weekly allowances.
- Pro 100, Pro 200 and Pro 500: the weekly allowance.
Each covered allowance below 100% goes back to 100%. One that is already at 100% is not restarted. Separate model or feature allowances, such as image generation and file uploads, are not touched. If you are not sure which clock gates you, the Pro-versus-Plus breakdown explains why Pro is weekly-only after the September 29 changes.
The 80% rule for banked resets#
You cannot redeem a banked reset whenever you like. From Usage settings, at least one covered allowance must have less than 80% remaining. Above that, OpenAI shows "Your usage does not need a reset right now" and the reset stays in your balance. The reset is only counted as used if it restores at least one allowance.
The desktop app also has an option, "Allow your assistant to use resets", which lets Codex redeem one for you. OpenAI says it needs your main 5-hour or weekly allowance at 10% or less remaining and asks for confirmation each time. In the CLI, /usage then Redeem reset is the path, and OpenAI says to fall back to the desktop app or web if your CLI version does not show the option.
Why your reset date moves#
This is the part the forums are loud about, and it is documented behavior, not a bug. A reset that restarts a usage period replaces the old schedule. OpenAI's own example: a weekly period due to end on Friday that restarts on Tuesday refreshes next the following Tuesday, and the Friday refresh no longer applies. Your billing date does not change.
For a purchased reset the rule is sharper. The new weekly period starts with your first request in Work or Codex after the reset is applied, and the next automatic weekly reset is seven days after that first request, "not necessarily 7 days after payment". OpenAI also says it "pulls your normal weekly allowance forward" rather than adding a separate entitlement.
The practical consequence: a reset is a trade, not a gift. If your weekly reset is two days away and you are at 20% remaining, a paid or banked reset buys you a lot. If it is two days away and you are at 75%, a reset can cost you the refresh you were about to get.
Automatic resets stack awkwardly with banked ones. OpenAI's example: use a banked reset at 10:00, burn 5% of the refreshed allowance, and a global reset at 10:30 takes you from 95% to 100%. The two do not add to 200%, and the banked reset is not returned. Unused banked resets stay in your balance with their original expiry.
What a builder does Monday#
- Find your real state. Desktop: Settings, Usage and billing, then check Available for banked resets and their expiry dates. CLI:
/usage(the pricing doc also lists/usage weeklyand/usage daily; see our limits guide for the full command list). - Do not use a banked reset above roughly 20% used unless it is about to expire. The 80% gate is a floor, not advice. A reset used late in the weekly window wastes the least.
- Check the next refresh date before and after any reset. OpenAI says a changed date alone does not mean another banked reset was used, so look at History (past 30 days) before assuming something was spent.
- Think twice before buying an instant reset. It applies immediately, cannot be saved, and OpenAI says it generally does not refund these. Compare it with simply funding usage with credits or an API key for the rest of the week.
- Cut burn instead of buying resets. If runs are what drain the allowance, budget them first - see Codex CLI resource budgets.
If you split work across vendors, the Anthropic equivalent is covered in the Claude Code usage limits playbook.
What people are actually saying#
- An OpenAI Developer Community thread posted this week from a Business seat says allowances jump back to 100% every few days with the next refresh shifted about seven days out, without any banked reset being redeemed. The poster argues this interferes with the 80% rule and with using banked resets before they expire. That is one user's account of their own seat, and the poster says they are not claiming to know OpenAI's intent.
- The same thread links related older topics in the Codex category tagged rate-limit-reset, including complaints that an automatic reset can reduce total usage. The pattern is consistent with the documented rule that a reset replaces the old schedule.
- On Reddit, r/codex threads such as Codex burning usage way faster after reset and Codex usage since last reset are titled around allowances draining faster after a reset. Treat these as anecdotes: meters, models and workloads differ, and we could not verify any of the figures.
- The counter-case: a reset that lands when you are at 10% remaining is a straightforward win, and one r/codex commenter in Burning through usage FAST says, per the search excerpt we could read, that they may not make it through the week without another reset. Separately, OpenAI documents that automatic resets do not appear in History, which is the opacity the forum poster objects to.
The strategic read#
Our read: resets work like a retention tool that avoids a limit change. Usage allowances are the real price of a plan, and a promotional reset lets OpenAI soften a tight week without touching the headline limits or the sticker price. The cost is a harder planning problem for teams: if the refresh date can move under you, a weekly budget is no longer a calendar. Expect competitors that sell flat plans, including Anthropic, to keep reset behavior and clear countdowns as a comparison point.
Continue Reading#
- Codex Usage Limits and Pricing in 2026 - what each ChatGPT plan buys and how the clocks work
- Claude Code Usage Limits in 2026 - the Anthropic side of the same question
- Codex CLI Resource Budgets - guardrails that stretch an allowance
- Sign in with ChatGPT: Run Coding Agents on Your Plan - how plan usage flows to other agents
Sources#
Get the next comparison like this in your inbox
One email a week on Codex and the rest of the AI dev stack. Free.
Read next on AI coding tools
Codex Usage Limits and Pricing in 2026: Pro 100, Pro 200, Pro 500, Resets, and 'Model at Capacity' Errors
Codex usage limits and pricing per ChatGPT plan: what Plus, Pro $200 and Pro $500 buy, how resets work, and what to do about 'Selected model is at capacity'.
14 min readClaude Code Usage Limits in 2026: The Practical Playbook for Pro and Max Teams
Claude Code usage limits are mostly an ops problem. A playbook for Pro and Max teams: lock auth mode, bound subagents, add hooks and route work by difficulty.
9 min readCodex CLI Needs Resource Budgets, Not Just Token Budgets
A trending Codex SQLite WAL bug is a useful warning for every local coding agent: logs, disks, background processes, and telemetry paths need budgets too.
8 min readNew here? Start with
Technical content at the intersection of AI and development. Building with AI agents, Claude Code, and modern dev tools - then showing you exactly how it works.
