Codex Reset for 25 Million Users: What Is Available Again

On August 31, 2026, another public Codex reset arrived: usage was reset for every paid ChatGPT Work and Codex subscription, according to the announcement. This time the reason was not an outage but a milestone of 25 million active users. People who had nearly exhausted a weekly allowance potentially regained room for coding tasks, reviews, and cloud runs.

The headline is simple; the operational meaning is not. A global post cannot tell you the percentage visible in your account at this moment, and one act of goodwill does not create a new subscription promise. This guide separates the confirmed event from what you still need to verify.

What was confirmed on August 31

The current primary post came from Tibo Sottiaux. It connects two statements: ChatGPT Work and Codex reached 25 million active users, and usage had been reset for all paid subscriptions to celebrate. The wording describes the reset as completed rather than merely forecast.

Creaiter added the event only after two independent trackers linked the same current X post. That check matters because a reset had already been promised for 6 p.m. Pacific the previous day, while an earlier near-duplicate post was later corrected. A single screenshot could easily mix those records.

What a global hard reset means

A hard reset refreshes affected usage automatically. It is different from a banked reset, which eligible users redeem later. It is also not credit for the OpenAI API. API billing, rate limits, and spending controls remain a separate contract.

The global event does not replace your regular account counters. Codex may show a short usage window and an additional weekly budget. Only your usage dashboard or Codex status view can reveal which values changed for your plan. Our evergreen guide to Claude and Codex limit resets explains those categories in more detail.

How to check whether your account received it

Open the usage view for the exact account and organization where you work. Record the weekly state, short window, and next personal reset time. Refresh the page if it was already open during the announcement. Then verify that you are looking at ChatGPT Work or Codex—not API billing or another ChatGPT limit.

If a counter does not jump to 100 percent, that is not immediate proof of failure. Rollout can become visible at different times, and surfaces may update differently. The public statement describes the intended audience; your dashboard describes your account. If it stays unchanged, record the plan, organization, time, and exact warning before contacting support.

How to spend the renewed capacity well

A reset tempts you to start the largest task on your backlog. A bounded work block is safer: one feature, one bug fix, or one release check. Define the outcome, affected files, and acceptance criteria before the run. A good first prompt saves usage by reducing detours, not merely by being short.

Reserve capacity for verification. An agent needs room to read, test, inspect, and correct—not only to write. Small commits or clear intermediate checkpoints make long sessions recoverable. When another limit appears, you know what is finished and where to continue.

Checklist for your next Codex block

• Account, organization, and usage view are verified.
• The desired outcome is bounded to one testable block.
• Relevant files and acceptance criteria are in the request.
• Capacity remains for tests, browser review, and corrections.
• The diff, test result, and next step are saved before the session ends.

Why you should not calculate the next date

Recent global resets sometimes landed close together. That still does not create a contract. Milestones, incidents, launches, and goodwill decisions have different causes. An average or median only describes previous events.

Use the Codex reset history to classify a signal, not to bet a release on it. Until another explicit source appears, the safe assumption is: no extra global reset is coming, and your personal usage timer remains authoritative. That turns the 25M reset into helpful extra capacity instead of the foundation of a risky delivery plan.