September 27 update: see the launch-offer guide for Claude’s banked reset and existing-subscriber cloud credits, OpenAI’s September 26 reset, and the limits of the DevDay rumors. Earlier dated policy analysis below retains its original verification scope.

September 27, 2026 update: current reset rules

I checked OpenAI’s current banked Codex reset help page and paid weekly Work and Codex reset help page on September 27, 2026. This dated update owns the current OpenAI reset mechanics; the August sections below preserve a historical analysis and should not be read as a current policy changelog.

Full banked reset. OpenAI says using a full banked reset refreshes both the five-hour and weekly Codex usage windows and changes the weekly reset date. Its example is explicit: if the normal weekly reset is Friday and an eligible user applies the reset and resumes Codex on Tuesday, the next weekly reset is around the following Tuesday; the user does not also receive the original Friday reset. The reset is consumed only when it successfully refreshes at least one eligible window. It remains a promotional, account-held benefit rather than credit, and eligibility, affected windows, delivery, and expiry vary by offer, plan, workspace, region, and account. Expiry is account/offer specific: check the expiry shown in the account; an unused reset that expires cannot be restored or reissued.

Paid weekly reset. OpenAI separately documents an immediate paid reset for eligible personal Plus and Pro accounts. A completed purchase restores both five-hour and weekly usage, pulls the normal weekly allowance forward instead of adding a second entitlement, applies immediately, and cannot be saved for later. The new weekly period begins with the first Work or Codex request after the reset, and the next automatic reset is scheduled seven days after that request. Availability varies by account; the current help page excludes Free, Go, Business, Enterprise, and Edu plans. This purchase is separate from a banked reset and from usage credits, so compare the account’s displayed price, remaining allowance, and next reset date before buying.

First use, idle time and the weekly clock

Weekly windows are not stored credits. Do not count two idle weeks as two allocations waiting to spend, or assume a second refill is due immediately after returning. A usage-triggered clock starts when you use it; doing useful work earlier can start that period earlier. Check the account’s displayed timing rather than assuming a calendar schedule or rollover.

OpenAI’s paid reset is an explicit example: allowance is restored immediately but the new weekly clock waits for the first request. After resuming, the next refill is seven days away, not an old reset one day away. If useful work is ready, start with a real bounded task and record the new reset time. Do not buy a reset or manufacture work merely to start a timer.

The Codex usage guidance directs users to their account’s limits and reset times; automatic provider resets are applied directly, not saved as extra weeks. The September buying guide applies these distinctions to planning useful work. Exact timing remains specific to the window and product.

The current help pages document these mechanics without making historical August community prices universal. Use the signed-in usage page for the account’s actual offers, windows, and expiry.

Historical August 2026 record

The sections below preserve the article’s August 20 analysis, including dated announcements, community observations, forecasts, and competitor context. Their current-sounding OpenAI statements are historical evidence; the September 27 update above is the current reset reference.

August 20 historical record: purchased full resets appeared on some accounts

Multiple dated community reports now show a purchased full reset offer on some Codex accounts. The observed prices are $8 on some Plus accounts and $80 on some Pro 20x accounts. These prices and the rollout remain community-observed: OpenAI has not published universal pricing, eligibility, plan coverage, refund terms, or availability for this control.

The reported mechanism matters more than the headline price. Redeeming the offer starts a new seven-day window and moves the next scheduled weekly reset to roughly seven days after redemption. It is therefore not a bonus week stacked on top of the old recovery date. Pro 5x, Business, universal availability, refund behavior, and exact eligibility remain unresolved.

This evidence does not show that paid resets replaced free promotional or incident resets. Provider-wide hard resets, banked promotional resets, purchased full resets, purchased credits, and scheduled recovery remain separate mechanisms. Check the signed-in usage page before making a purchase and compare the account’s displayed price with the value of waiting, switching lanes, or buying credits.

August 13 historical record: a 15M-milestone reset, not a new entitlement

At 01:01 UTC on August 13, 2026, OpenAI product lead Tibo Sottiaux said Codex had crossed 15 million active users and told “everyone” to enjoy a reset expected within roughly an hour. The direct announcement establishes the event and its milestone framing. It does not create a permanent reset schedule, a banked grant, or an every-million entitlement.

The distinction matters because the prior public promise ended at 10M. On August 12, Sottiaux said explicitly that he had promised a reset for every additional million active users only through 10M, then teased a surprise after growth passed that point.

The recent provider-wide sequence is unusually dense:

For future teases, the practical feed is Tibo Sottiaux on X. Treat it as a volatile announcement stream, not a policy changelog or a substitute for the signed-in usage page.

Historical analysis: non-rollover capacity has an expiry cost

An AI subscription meter is not a wallet. It grants service capacity under a provider’s current rules, often inside weekly, session, model-specific, or credit-based accounting. If unused allowance does not roll over, it is perishable: scheduled recovery or a provider-wide reset can erase the opportunity to use what remained.

Ration too aggressively and an expiry or surprise reset can erase useful option value. Spend too aggressively and you may lack capacity for urgent work. The goal is useful accepted work per subscription period, with a reserve—not the highest possible token burn.

Historical framework: six mechanisms that should not be mixed

MechanismWho controls itWhat happens
Scheduled recoveryPublished plan clockThe old window ends; unused allowance normally does not roll over
Provider-wide hard resetProviderThe announcement’s group receives a fresh meter automatically
Incident or promotional resetProviderScope and reason depend on the named event
Banked resetEligible user until expiryThe user chooses when to refresh the applicable limit
Purchased full resetEligible purchaser; account-scoped rolloutCommunity reports describe a fresh seven-day window whose next recovery date moves with redemption
Purchased usage creditsAccount or workspace purchaserWork can continue after included limits; counters are not documented as refilled

The labels protect against false equivalence. A broad hard reset is not cash or a credit deposited into an account. A banked reset is expiring functionality, not permanent rollover. OpenAI pricing says available credits let work continue after included limits; it does not say purchased credits restart a five-hour window or refill a weekly meter.

Historical August view: five-hour windows were documented while observed accounts showed weekly-only

At the August 20 review, OpenAI’s pricing page described shared five-hour windows and possible additional weekly limits. That was the documented policy surface then; the current reset mechanics are recorded in the September 27 update above.

Observed August account behavior differed from that documentation. Reports showed weekly-only displays after the announced July 30 restoration date. Their August enforcement and future policy state were unresolved/uneven because account behavior could differ. “Active for every account,” “not in use anywhere,” and “permanently removed” would each have overstated the August evidence.

AIHackers’ August 20 forecast did not expect dependable five-hour enforcement to return in the near term. That was a dated forecast, not an OpenAI commitment, and the current primary docs now establish that a full reset refreshes the five-hour window.

Historical August view: the broad July grant reached its expiry window

OpenAI’s June 11 release notes say banked resets are usable for 30 days after grant. On July 12 at 21:28 UTC—July 13 in Singapore—Sottiaux announced a 500,000-user grant and said the first broad banked reset for ChatGPT Work and Codex users would follow for the 7M milestone.

The bounded August 13 source review found no later directly announced broad banked grant. That was an August evidence boundary, not a current claim: OpenAI’s current help page now records September 3 and 4 banked resets for eligible Plus, Pro, and Business accounts. A grant made around July 13 would therefore have reached its 30-day window around August 12–13, subject to the exact grant timestamp and applicable offer terms.

Dated Reddit reports describe grants disappearing near or before the displayed expiry and, in some cases, without the notification users expected. Those reports are community-observed, not proof of universal behavior, backend intent, or a formal end to banked resets. Current referral offers can still grant a reset, usage, or another benefit under offer-specific terms.

Historical analysis: game theory of frequent surprise resets

Frequent broad resets can function as an acquisition and retention subsidy. They lower the experienced cost of trying a demanding model, keep rate-limited users active, and can help form a habit before standard limits become the dominant constraint. Tying resets to user milestones also creates a compact X marketing loop: growth produces an announcement, the announcement produces attention, and the reset gives current users a reason to reopen the product.

If spare compute exists at particular times, a discretionary reset may improve reserve-capacity utilization. But the same event can raise aggregate burn by weakening the incentive to ration. It can also create adverse selection: power users are most likely to watch the feed, exhaust allowance before a teased reset, and capture a larger share of the subsidy.

That creates reset moral hazard. Once users expect another refresh, conserving capacity becomes less attractive; some community posts explicitly describe accelerating usage before a promised reset. A forced reset can also destroy remaining allowance for users who did conserve, which makes timing feel arbitrary and encourages even more anticipatory burn next time.

The likely pressure is toward a more explicit accounting system: transparent credits, user-controlled grants, fixed promotional boosts, or tighter and more predictable limits. None of those outcomes is guaranteed. The key falsifier is whether broad discretionary resets remain frequent without a move toward clearer metering or narrower eligibility.

Competitor promotions use different accounting

ProviderCurrent promotion or changeWhat it is not
AnthropicSeptember 14 vendor update: the 50% Claude Code weekly-limit increase ended September 13. Weekly limits are now 25% above the pre-promotion baseline for Pro, Max, Team, and seat-based EnterpriseNot a hard reset or an additional 25% on top of the former boost; no universal task count or measured account capacity follows
Z.AISince July 30, new GLM Coding plans use transparent token-based credits; active legacy plans keep their existing calculation through the current cycle, eligible Legacy V2 plans remain renewable/upgradable, and weekends use off-peak treatmentNot a Codex-style hard-reset program and not proof of sustainable unit economics

Anthropic’s updated terms, checked September 14, supersede this page’s August 31, 2026 at 11:59 PM PT expiry snapshot. The former promotion excluded Free and consumption-based Enterprise; five-hour and other Claude/Cowork limits were unchanged. The new notice is vendor evidence; account capacity and archive replay remain unverified. Z.AI’s July 30 notice separates new credit metering from legacy five-hour/weekly quotas and preserves a migration incentive. Z.AI’s referral rules separately offer an eligible invited user 10% off the first GLM Coding order.

These are useful contrasts in predictability and accounting. They do not show that Anthropic or Z.AI copied OpenAI, and promotions do not prove that any provider’s economics are sustainable.

Historical August community pulse: a bounded sample, not a survey

The earlier bounded sample covered reactions to the August 8 reset, anticipatory burn around the promised Monday reset, a banked reset expiring early, and uneven reports about whether the five-hour limit returned. The August 20 refresh adds reports of an $8 Plus reset, an $80 Pro 20x reset and shifted recovery date, and uneven rollout plus one reported purchase.

Themes include rapid burn, unpredictable reset value, concern about long-run sustainability, confusion over expiring grants, and speculation that paid resets may eventually replace gifts. This small self-selected sample is not representative. It establishes questions and observed behavior, not provider policy, motive, account-wide prevalence, or a future paid-reset product.

A practical policy without quota burning

Keep a ranked backlog of real quota-heavy work: repository review, research synthesis, migrations, test generation, documentation repair, or a bounded refactor. When capacity is available, pull the highest-value item forward. Keep an urgent-work reserve based on what could reasonably arrive before the displayed recovery time.

If the reserve is threatened, switch routine work to a smaller model where quality remains acceptable. Before purchasing overflow, check the current dashboard for the actual options on the account. Do not manufacture prompts, retries, or subagents merely to drain a meter before a teased reset.

Falsifiable August 20 forecast

AIHackers expects weekly capacity plus account-scoped paid overflow and discretionary promotional resets to remain a plausible near-term equilibrium, without documented universal five-hour enforcement or routine broad banked grants. This forecast fails if OpenAI publishes materially different reset terms, restores dependable five-hour enforcement across accounts, begins routine broad banked grants, or removes the paid-reset control.

For the dated record, use the reset chronology. The Codex claim ledger tracks evidence status. For subscription-versus-API buying decisions, use AI Value, the Deals ledger, and the LLM cost-saving playbook.

Frequently asked questions

Is unused subscription capacity the same as purchased tokens?

No. A plan meter is a time-limited service allowance, not owned API tokens, cash, credit, or a transferable balance.

Did idling cause the recent Codex resets?

No evidence supports that causal claim. Provider-wide resets refresh the announced group regardless of one user’s remaining allowance.

Does every reset reach every plan?

No. Current banked-reset eligibility and paid-reset availability vary by offer, plan, workspace, region, and account. The August 8, 11, and 13 announcements below are historical scopes; the signed-in usage page remains the authority for an account.

Is the Codex five-hour limit active?

OpenAI’s current banked-reset and paid-weekly-reset help pages say a full reset refreshes both the five-hour and weekly windows. That documents reset behavior, not universal availability or account state, so use the signed-in account as the operational authority.

Should I exhaust my allowance before a teased reset?

No. Pull forward valuable work from a ranked backlog, retain an urgent-work reserve, and do not manufacture work merely to empty a meter.

How is a banked reset different from a hard reset?

An eligible user controls an expiring banked reset. A provider-wide or global reset automatically refreshes the announcement’s group. OpenAI’s current help page records September 3 and 4 banked resets for eligible Plus, Pro, and Business accounts, with eligibility and expiry varying by offer and account.

Is a purchased full reset the same as buying credits?

No. OpenAI documents a paid weekly reset as an immediate, eligible-account purchase that restores five-hour and weekly usage and starts a new weekly period after the first Work or Codex request. Credits fund supported work after included limits, while a banked reset is saved for later; all three are separate.

Where should I check current limits and reset announcements?

Use the signed-in usage page for account state, OpenAI’s banked-reset help page and paid-weekly-reset help page for current mechanics, and OpenAI pricing for documented policy. Tibo Sottiaux’s X feed carries historical reset teases, but it is not a formal policy changelog.

Sources

Current OpenAI reset mechanics checked: September 27, 2026. The historical August analysis was last verified August 20, 2026; limits, promotions, reset scope, prices, commands, account behavior, and unofficial forecasts can change.