Twenty million. Six days after confirming 15 million, OpenAI's Codex lead posted the next number — and this time the reset lands on your schedule, not his.
On August 21, 2026, Tibo Sottiaux (@thsottiaux), OpenAI's Codex and ChatGPT engineering lead, posted: "It's me again. I come bearing great news. First of all, we have hit 20M active users for Codex some time this week. Second of all, this is cause for celebration and during the day we will credit every Codex and ChatGPT Work user with a BANKED reset that you can use at your own leisure." He closed with: "we will have some other good news later too."
That is a fast jump from the 15 million milestone explainx.ai covered on August 13 — roughly 5 million more active users in about a week, and the fourth Tibo-announced growth milestone since 8 million on July 14.
This is also his second post of the day. Earlier on August 21, Tibo published a separate explanation about why some Codex usage limits felt inconsistent across accounts — tracing many complaints to sub2api, an unsupported subscription-to-API sharing pattern. That story is fully covered in explainx.ai's sub2api and Sign in With ChatGPT post — this post does not repeat it; it covers the growth number and the reset mechanic that landed hours later.
Update — August 22, 2026: The banked reset promise did not land on schedule, and the story turned skeptical overnight. Late on August 21, Tibo posted a firmer deadline — "The banked reset will be there by 8pm PST. For all paid users of ChatGPT Work and Codex. Do with this information what you may." — but 8pm PST came and went without the reset appearing for many accounts. Users piled into replies asking whether anyone had actually received it ("did anyone already get their banked reset?"), and BridgeMind summarized the gap bluntly: "We are giving everyone a banked reset today — the reset: nowhere to be found." Journalist Ed Zitron (@edzitron) escalated the criticism past a missed deadline, arguing OpenAI is quietly tightening limits while denying it: "OpenAI has clearly cut rate limits and is outright denying it," and separately, on the reset specifically: "Tibo promised a banked rate limit reset, then did not deliver one — absolute marketing masterclass." Zitron's broader point: Tibo, who previously issued resets for "basically any reason," is now telling users OpenAI is "not seeing anything abnormal" about faster-draining limits, then promising a fix that has not shown up. Treat the 20M figure and the reset offer as confirmed by Tibo — the reset's actual delivery is not, as of this update. Check your usage page directly rather than assuming the credit has arrived, and see the 15M milestone post for how the prior reset promise played out by comparison.
TL;DR — what people are asking
| Question | Answer (Aug 21, 2026) |
|---|---|
| Did Codex hit 20M? | Tibo, yes — "some time this week," company-reported, not audited |
| Codex-only or Codex + Work? | Pledge language says Codex; the reset credit goes to both surfaces |
| What did OpenAI actually ship today? | A banked reset credited to every Codex + ChatGPT Work user |
| Is the reset forced right now? | No — it is banked, meaning you apply it whenever you want |
| Did the reset actually arrive by the promised 8pm PST? | Disputed — Tibo set that deadline late Aug 21, but many users reported no reset as of Aug 22; see update above |
| Does it stack with resets I already had? | Likely yes — Tibo has previously described users holding three banked resets at once |
| What is the sub2api story from this morning? | A separate post — see the dedicated sub2api writeup |
| What is the "other good news"? | Unconfirmed as of publication — no follow-up post yet |
| Is this a plan upgrade? | No — another manual Tibo-issued credit, same pattern as July and August |
What Tibo actually said
Two sentences carry the whole announcement. Read them exactly, not paraphrased into a bigger claim.
"It's me again. I come bearing great news. First of all, we have hit 20M active users for Codex some time this week. Second of all, this is cause for celebration and during the day we will credit every Codex and ChatGPT Work user with a BANKED reset that you can use at your own leisure." — Tibo Sottiaux, X, August 21, 2026
"we will have some other good news later too." — Tibo Sottiaux, same post
| Claim | Status |
|---|---|
| Codex crossed 20M active users | Confirmed (Tibo; "some time this week") |
| Every Codex + ChatGPT Work user gets a banked reset | Confirmed (Tibo; credited "during the day") |
| The reset is banked, not forced immediately | Confirmed — explicit "use at your own leisure" wording |
| More good news is coming | Teased, unconfirmed — no specifics, no timing given |
| Reset stacks with prior banked credits | Not stated in this post — inferred from prior behavior, see below |
| The banked reset arrived by the promised 8pm PST deadline | Disputed — Tibo set the deadline, users reported it "nowhere to be found" as of Aug 22; see the update above |
explainx.ai read: the headline number is the hook, but the mechanic is the real news. Every prior Tibo reset — 8M, 15M, and the August 9 paid-plan refill — landed as an immediate top-up on a fixed clock. This one is explicitly banked: it sits on your account until you choose to spend it.
Growth timeline — 8M to 20M in five weeks
| When | Figure | Whose number | Notes |
|---|---|---|---|
| Feb 2026 | ~1M | Launch baseline | Desktop Codex era |
| Jul 12 | 6M active | Tibo | Same day as the temporary 5-hour removal |
| Jul 14 | 8M active | Tibo | Codex + ChatGPT Work combined |
| Jul 21 | ~10M | Community | Tibo's own +1M-until-10M pledge ceiling |
| Aug 13 | 15M active | Tibo | Reset landed "within the hour"; see 15M coverage |
| Aug 21 | 20M active | Tibo | Banked reset credited to every user, no forced timer |
Five million net new active users between the 15M and 20M posts, in roughly a week — the tightest gap yet between two Tibo-confirmed milestones. Unlike the silent stretch past 10M, OpenAI is now shipping a reset at every checkpoint rather than letting the promise lapse.
What "banked reset" actually means
This is the term worth defining precisely, because it changed shape between milestones.
| Reset type | How it lands | Example |
|---|---|---|
| Immediate reset | Your usage meter refills the moment OpenAI flips the switch | Aug 13's "landing in the next hour" 15M reset |
| Banked reset | A credit sits on your account; you trigger it whenever you want | Aug 21's 20M reset |
Banked resets are not new to Codex — OpenAI first rolled them out in mid-July 2026 alongside GPT-5.6 Sol, as covered in explainx.ai's July banked-reset post. What is new is using the mechanic for a growth-milestone celebration instead of a mid-week capacity fix.
Do banked resets stack? Tibo's own earlier posts say yes. In a prior reset-week thread, he described issuing a hard reset specifically because "some users had stacked up to three banked resets already that they can apply on their own schedule." That means the August 21 credit is very likely additive on top of anything you were already holding — check your usage page rather than assuming a fresh single credit replaced an old one.
explainx.ai's dictionary now tracks this term — see the banked reset entry for the standalone definition.
The same-day pairing: banked reset vs sub2api
Two Tibo posts, same day, easy to conflate. They are not the same story.
| Sub2api post (earlier, Aug 21) | 20M / banked reset post (later, Aug 21) | |
|---|---|---|
| Subject | Fraud investigation into why some accounts drain faster | Growth milestone + reward |
| Root cause discussed | Subscription-to-API proxy sharing, flagged by fraud systems | None — this is a celebration, not an investigation |
| Action for readers | Stop routing through sub2api; use Sign in With ChatGPT | Check your usage page for the new banked credit |
| Full coverage | sub2api and Sign in With ChatGPT guide | This post |
If your account still feels tight after this banked reset lands, the sub2api post is the one to read next — it is the more likely explanation for persistent drain than anything described here.
Practitioner guide — how to spend a banked reset
Because it is banked, you control timing. That changes the calculus from "use it now before it's gone" to "use it when it matters most."
| Do | Don't |
|---|---|
| Save it for a blocked migration, review pass, or long agent loop | Trigger it immediately on toy prompts just because it exists |
Check /status and your usage UI to see the stacked banked count | Assume only one credit is available if you already had one banked |
| Apply it before a known heavy week (release crunch, big refactor) | Let it sit indefinitely if your plan caps banked inventory |
| Confirm whether it applies to Codex, ChatGPT Work, or both in your account | Mix up this credit with the 5-hour vs weekly caps, which are separate mechanisms |
Copy-paste check before you spend it:
1. Open Codex / ChatGPT Work usage UI — look for a "banked reset available" indicator
2. Count how many banked resets are stacked (could be 1-3+)
3. Pick the highest-value blocked job, not a backlog of small tasks
4. Apply the banked reset, then confirm the weekly/5-hour bar actually moved
What is still unknown
- Whether the banked reset ever fully landed. Tibo promised delivery "by 8pm PST" for all paid ChatGPT Work and Codex users late on August 21; as of the August 22 update, multiple users reported no reset on their account and no confirmation from Tibo that it shipped.
- Whether limits were quietly tightened. Ed Zitron's claim that "OpenAI has clearly cut rate limits and is outright denying it" is his characterization, not an OpenAI admission — treat it as an escalating critique, not a confirmed fact, until OpenAI directly addresses it.
- What the "other good news" is. No follow-up post existed as of publication. Treat any guess (new model, pricing change, feature drop) as speculation until Tibo or OpenAI confirms it directly.
- Whether 20M is Codex-only or combined. The milestone language echoes the Codex-specific pledge wording; the reset credit explicitly covers both Codex and ChatGPT Work.
- How long the banked credit stays valid. OpenAI has not published an expiration window for this specific credit — earlier banked-reset behavior suggests it persists until spent or superseded by a hard reset.
- Active-user methodology. OpenAI still has not published a definition (30-day active, weekly, per-surface) for any of these milestone numbers.
Summary
Codex and ChatGPT Work crossed 20 million active users, per Tibo Sottiaux's August 21, 2026 post — up from 15 million just over a week earlier. To mark it, OpenAI credited every Codex and ChatGPT Work user a banked reset they can apply on their own schedule, rather than forcing an immediate meter refill. Tibo also teased more news later, which had not landed as of this post.
Update, August 22: the promise slipped. Tibo set an 8pm PST delivery deadline for all paid ChatGPT Work and Codex users, but that window passed with many users reporting no reset on their account. Ed Zitron publicly called it a "marketing masterclass" of promising a reset and not delivering, alongside his broader claim that OpenAI has cut rate limits while denying it. Neither the 20M figure nor the reset offer is in dispute — only whether OpenAI actually delivered the reset it promised, on the schedule it promised.
Read this alongside the same-day sub2api investigation if your account still feels limit-starved after the reset — that is the more likely explanation than anything in this growth announcement. Follow @explainx_ai for the next Tibo milestone.
Related on explainx.ai
- Codex usage limits and sub2api — Tibo on fraud vs Sign in With ChatGPT (Aug 21)
- Codex 15M users — Tibo reset tease (Aug 13)
- Codex + ChatGPT Work hit 8M users (Jul 14)
- Limit Reset Day — Claude, Codex, Cursor (Jul 16)
- GPT-5.6 Sol thinking budget + banked resets (Jul 13)
- OpenAI starts selling usage resets — up to $80 on Pro (Aug 16)
- Tibo vs Boris — Aug 9 paid Work/Codex reset
- ChatGPT Work vs Codex — complete guide
- Banked reset — dictionary entry
Sources: Tibo Sottiaux on X (August 21, 2026); Tibo's 8pm PST reset deadline post and Ed Zitron on X (both August 21-22, 2026).
User counts and reset timing reflect Tibo's August 21, 2026 public post. Active-user definitions are not independently audited. Limit policies are temporary gifts unless OpenAI publishes a plan change — verify meters in-product before you schedule a production sprint.