The evidence behind the headline

Watch the source.

Provider posts, replies and community leads. Every signal keeps its provenance and its unanswered questions.

Hourly automated watch (GitHub Actions) plus editorial review. Hourly: recent posts from each X account are keyword-filtered and classified by a small model. Explicit full or banked resets from provider accounts are filed automatically with a verbatim quote and receipt; everything else opens a review issue. X access can fail; failures are logged, never read as no news.. This is not a continuous X firehose. The separate 15-minute notification job distributes reviewed reset announcements.

Latest linked-source review: . Forty-two linked reset originals rechecked through X syndication without changed terms or retraction. No new provider post establishes Day 13 delivery, eligibility or reset mechanics; the standalone 'Done' remains contextually ambiguous. Twelve of 13 recent-post feeds responded after retries; SpaceXAI remained HTTP 404, so discovery coverage is degraded. Other new provider and community posts add no reset remedy. Public Tibo timeline returned HTTP 429, OpenAI help pages HTTP 403 and Cursor checking inaccessible. The preceding executed editorial check was October 18 at 00:36 UTC. The September 22 Tuesday/3am timezone and Pro 500 make-up remain unresolved.

Confidence ladder

Big news. Clear labels.

  • Developing: a primary timing hint or incomplete reset signal. No reset promise inferred.
  • Strong signal: an explicit primary reset indication, with important details still missing. An editorial grade, not a probability.
  • Reset announced: an explicit primary commitment with named scope. Delivery is still pending.
  • Reset confirmed: a primary source reports delivery. Individual accounts may differ.

Community copies do not count as independent confirmations. Blue checks do not prove employment. Unknown timezones never become countdowns. Unreviewed signals lose their active label after six hours; expired windows leave the spotlight.

See signals beside the statistical forecast →

Current evidence

Day 13 limit reset promised by EOD PST.

Window passed · An explicit provider reset promise with a same-thread timing follow-up. Scope and mechanics are missing, so this is a strong signal pending delivery, not an announced reset with named scope or a confirmed reset.

“Day 13/ Le limit reset”
@thsottiaux ↗

Complete original post, author and timestamp verified through X syndication. The attached illustration does not supply eligibility or mechanics.

“Landing sometime today by EOD PST”
@thsottiaux ↗

Complete original reply, author, timestamp and direct parent ID verified through X syndication. No UTC deadline inferred.

Still missing: Eligible products, plans and accounts · Full versus banked mechanics and affected usage windows · Provider completion statement and account-level delivery

Read the developing story →

Day 10 reset reported done.

Window passed · The verified completion post quotes the two-hour follow-up to Tibo’s Day 10 reset announcement. This confirms provider-reported completion within the announced window, not individual account delivery. No product scope or reset mechanism is stated.

“Done and dusted”
@thsottiaux ↗

Complete original, author, UTC timestamp and quoted two-hour reply verified through X syndication. Provider-level completion statement, not account-level audit.

“Landing within the next 2 hours”
@thsottiaux ↗

Complete original, author, UTC timestamp and direct reply to Day 10 reset post verified through X syndication.

“Day 10/ Reset”
@thsottiaux ↗

Quote is a verbatim excerpt of the complete original post, verified through X syndication.

Still missing: Named products, plans and eligible accounts · Full versus banked mechanics and affected usage windows · Account-specific delivery and timing

Read the developing story →

Day 8 global reset reported done.

Window passed · The verified provider post quotes the Day 8 global-reset promise and states “It's done.” This confirms provider-reported completion. Do not infer account-specific delivery, full/banked mechanics or eligibility.

“What would you like with your side of reset? It's done.”
@thsottiaux ↗

Complete original post, author and timestamp verified through X syndication. This post quotes his Day 8 EOD PST global-reset promise; provider-level completion, not account-level audit.

“Global reset landing by EOD PST time. Enjoy”
@thsottiaux ↗

Complete original reply, author, timestamp and parent post ID verified through X syndication. Quoted by the completion post.

“Day 8/ Reset”
@thsottiaux ↗

Complete original post, author and timestamp verified through X syndication.

Still missing: Named products, plans and eligible accounts · Full versus banked reset mechanics and affected usage windows · Account-specific delivery times

Read the developing story →

Day 6 global reset reported propagated.

Window passed · Tibo’s verified follow-up quotes the original Day 6 global promise and explicitly says all propagated. This is provider-level delivery confirmation for that announcement, not an account-by-account audit. Exact eligibility and reset mechanics remain unstated.

“Put the reset in the bag. All propagated.”
@thsottiaux ↗

Complete original statement, author, timestamp and quoted-post ID verified through X syndication. This directly quotes the Day 6 global-reset promise, linking the provider completion claim to that announcement; it does not prove each account’s delivery or specify mechanics.

“Day 6/ Reset”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. This states a Day 6 reset but no scope or mechanics.

“Global reset by EOD. May the tokens do good things for you.”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. EOD timezone is not stated and the future-tense promise does not confirm delivery.

Still missing: EOD timezone and exact promised deadline · Named products, plans and eligible accounts · Full versus banked reset mechanics and affected usage windows · Account-specific delivery and propagation times

Read the developing story →

Day 3 banked reset confirmed for paid accounts.

Window passed · The original provider follow-up quotes the Day 3 announcement and explicitly confirms delivery. File as a confirmed banked reset for the announced paid-account scope. The completion statement does not specify affected windows or individual delivery time.

“Loading a banked reset in everyone's paid accounts. See you again tomorrow!”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication; the original X permalink returned HTTP 200. The in-progress wording announces loading but does not confirm completed delivery.

“Confirmed landed across all accounts. How are we doing so far?”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. This follow-up quotes Day 3 announcement ID 2107913674593644711, linking confirmation to the banked reset. It is a provider-level delivery statement, not proof of each account’s delivery time.

Still missing: Affected usage windows and products · Account-specific delivery and propagation timing · Any claim deadline

Read the developing story →

Day 2 ends with a processed reset.

Window passed · Tibo explicitly says the community demanded a reset and that the reset has been processed. Advance to confirmed delivery. Keep it outside typed reset history, calendar and subscriber feeds because eligibility, automatic-versus-banked mechanics and affected usage windows remain unstated.

“Over the next 28 days, each day we’ll either ship one thing that is a clear improvement and relevant for most codex/work users or ship a full reset. Let the improvements begin.”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. The either/or wording makes full resets possible but does not guarantee one or state any reset day.

“This Auto-review feature is now free and does not draw usage from your plan.”
@thsottiaux ↗

Original note-tweet opening, author and timestamp verified through X syndication; complete note text recovered from fxtwitter only after matching X's authoritative opening. This is a delivered usage-policy improvement, not a reset.

“OK this one is smaller, but we removed some friction for when building on the API. Happy building.”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. OpenAI Developers supplies the concrete API tier change; this post does not state a reset.

“No dodge, just three updates today”
@thsottiaux ↗

Complete original reply, author and timestamp verified through X syndication. It does not identify the third update, promise a reset or state delivery timing beyond today.

“2.1/ Approve for me (auto-review) is now included and does not use usage. 2.2/ Simplified API for builders. 2.3/ Meeting notes integrated. 2.4/ Decisions API live for builders.”
@thsottiaux ↗

Original author, timestamp and all four numbered items verified through X syndication. The final sentence is truncated after its opening words; the four-item list itself is complete. None is described as a reset.

“Four updates or a reset. Or both. How was day 2.”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. It clarifies that improvements and a reset can share a day, but does not announce a reset or report delivery.

“I do like giving resets”
@thsottiaux ↗

Complete original reply, author, timestamp and parent criticism verified through X syndication. It expresses preference rather than a reset commitment.

“Therefore ... the reset has been processed. Enjoy!”
@thsottiaux ↗

Original X page returned HTTP 200 with the complete delivery sentence. X syndication independently verifies author, timestamp and matching opening but truncates before the final words. Eligibility, mechanics, affected windows and account-specific delivery time are unstated.

Still missing: Reset eligibility and plan scope · Automatic versus banked reset mechanism · Affected usage windows and products

Read the developing story →

Global reset propagated, but some Pro 500 accounts missed it.

Window passed · Tibo's 04:28 UTC reply admits he did not propagate the reset perfectly at 10am, apologizes and says it will be better planned next time. His 04:01 UTC post reports that some Pro 500 accounts missed the reset and promises investigation and make-up. Keep the global reset confirmed while marking rollout delivery incomplete; affected count, cause, remedy, reset mechanics and usage windows remain unknown.

“Yeah no, that was my bad for not propagating it at 10am quite perfectly. This is something that will be better planned next time, apologies.”
@thsottiaux ↗

Complete original reply, author, timestamp and parent relationship verified through X syndication. It admits imperfect 10am propagation and promises better planning next time, but does not establish affected count or current remedy.

“Seeing some reports that the Pro 500 didn’t get the reset as expected earlier. Investigating and will make up for it”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. It reports an unresolved delivery exception for some Pro 500 accounts but does not state affected count, cause or remedy.

“Reset all propagated. Enjoy.”
@thsottiaux ↗

Complete original statement, author, timestamp and quoted-post relationship verified through X syndication. Quoting the all-paid-accounts announcement ties completion to that scope. Mechanics and affected usage windows remain unstated.

“Global reset landing tomorrow 10am PST for all paid ChatGPT accounts.”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. Posted October 1 at 7:14pm PST, so 'tomorrow' is October 2. The post explicitly names 10am PST and all paid ChatGPT accounts; mechanics and delivery remain unstated.

“Because usage on your primary dot is virtually unlimited at the moment, I can’t really give a reset. I need to come up with something new fast.”
@thsottiaux ↗

Complete original statement, author and timestamp verified through X syndication. It materially qualifies the earlier reset promise but does not name a replacement benefit.

“@giadotai Sorry Gia. More resets coming next week”
@thsottiaux ↗

Original reply, author, timestamp and parent relationship verified through X syndication. Eligibility and reset mechanics are unstated.

“The reset came right after my own reset, couldn’t be worse timing.”
@giadotai ↗

Community reply quoting the September 26 completion post. Establishes conversation context, not reset eligibility or mechanism.

Still missing: Pro 500 affected count, cause and promised make-up remedy · Reset mechanics: full, banked or another form · Affected usage windows and products within ChatGPT accounts

Read the developing story →

Claude’s saved reset: use by October 22.

Window passed · Provider explicitly reports the banked grant available in Settings → Usage. This completes the existing grant’s availability review; no duplicate ledger event or automatic meter reset. Separate short editorial spotlight for newly verified terms; the original September 23 visibility window remains expired.

“If you're on Pro, Max, or Team, your reset is available today in Settings → Usage. Apply it any time until Oct 22.”
@ClaudeDevs ↗

September 22 reply newly reviewed September 26. Confirms availability of the existing banked grant, not an automatic meter reset. Cutoff time and timezone are unstated.

“We’re also providing subscription users a rate limit reset, which you can save and use whenever you choose.”
@claudeai ↗

Original provider announcement verified through X syndication.

“Pro, Max, and Team users get a reset to use anytime”
@ClaudeDevs ↗

Provider account verifies eligible plans.

“Pro/Max/Team gets a banked reset! Go to Settings → Usage”
@lydiahallie ↗

Original reply verified; official provider accounts establish scope independently.

Still missing: Exact October 22 cutoff time and timezone

Read the developing story →

Codex resets have all propagated.

Window passed · Provider explicitly reports reset propagation complete. Scope comes from the same-day promise; community claims about non-banked mechanics are not promoted to provider facts.

“Resets all propagated. That will be all. Have a fantastic weekend.”
@thsottiaux ↗

Complete original statement, author and UTC timestamp verified through X syndication. Confirms propagation; the earlier same-day promise supplies paid-user scope.

“we’ll reset usage limits for all paid users across codex and ChatGPT work”
@thsottiaux ↗

Complete promise, author and posting time verified through X syndication. Future tense does not confirm delivery.

“codex users the reset is propagated now.”
@somehowali ↗

Original text verified through X syndication on September 26 at 17:34 UTC. Community observation only; no provider completion, mechanism or eligibility proof. Attached image was inaccessible through the image reader.

Still missing: Automatic versus banked reset mechanism · Affected usage windows

Read the developing story →

Codex banked reset announced.

Window passed · Reset announced: complete original provider post verifies an active banked-grant rollout and named plans. Community arrival reports remain separate from provider completion.

“We are loading a banked reset into all accounts of our Plus, Pro and Business users.”
@thsottiaux ↗

Complete reset sentence verified in two direct original X page responses (HTTP 200), including visible article text. X syndication and the prior official-embed screenshot truncate before this paragraph. Browser access remains HTTP 403; original-response provenance is stored with the receipt.

“We are almost Tuesday and I promised a reset for Tuesday.”
@thsottiaux ↗

Explicit reset promise verified through X syndication. No eligible plans or timezone in this post.

“3am on a tuesday”
@thsottiaux ↗

Original post verified through X syndication. A timing hint, without reset scope.

“OK fine. But it’s also still coming in Tuesday”
@thsottiaux ↗

X syndication verifies this is a direct reply to Udi’s request for a banked reset. Its relationship to the separate 3am reply remains an inference.

“you owe us a banked reset”
@udiWertheimer ↗

Original parent request verified through X syndication. Establishes the reply context, not provider authority or reset delivery.

“tibo and i are giving you a reset tuesday 3 am”
@LDT0545 ↗

Original community post verified through X syndication; quotes Tibo’s 3am reply. No established OpenAI affiliation or independent provider confirmation.

“Everybody the codex reset finally arrived.”
@somehowali ↗

Original community observation verified through syndication; not provider confirmation or proof of all-account delivery.

Still missing: Timezone for the earlier 3am hint · Provider confirmation of universal delivery completion

Read the developing story →

Claude adds a reset you can save.

Window passed · Provider explicitly reports the banked grant available in Settings → Usage. This completes the existing grant’s availability review; no duplicate ledger event or automatic meter reset.

“We’re also providing subscription users a rate limit reset, which you can save and use whenever you choose.”
@claudeai ↗

Original provider announcement verified through X syndication.

“Pro, Max, and Team users get a reset to use anytime”
@ClaudeDevs ↗

Provider account verifies eligible plans.

“Pro/Max/Team gets a banked reset! Go to Settings → Usage”
@lydiahallie ↗

Original reply verified; official provider accounts establish scope independently.

“If you're on Pro, Max, or Team, your reset is available today in Settings → Usage. Apply it any time until Oct 22.”
@ClaudeDevs ↗

September 22 reply newly reviewed September 26. Confirms availability of the existing banked grant, not an automatic meter reset. Cutoff time and timezone are unstated.

Still missing: Exact October 22 cutoff time and timezone

Read the developing story →

Source registry

Where we look.

  • Tibo · Codex ↗

    Posts, replies and quoted-post context; explicit reset verbs, timing and scope

    Primary statements
  • OpenAI ↗

    Launches, quota changes and reset announcements

    Provider account
  • OpenAI Developers ↗

    Codex announcements and replies

    Provider account
  • OpenAI status ↗

    Quota incidents and recovery; recovery alone does not prove a reset

    Provider status
  • Claude ↗

    Model launches and launch-day limit offers; check full threads, resets often sit in a reply

    Provider account
  • Claude Developers ↗

    Claude Code limits, banked credits and Max resets

    Provider account
  • Anthropic ↗

    Plan changes, launch offers and explicit resets

    Provider account
  • Lydia Hallie ↗

    Claude Code statements; verify current role and exact scope

    Named source
  • Claude status ↗

    Usage-limit incidents and remedies

    Provider status
  • SpaceXAI · xAI ↗

    Grok releases and quota announcements; account linked from the official x.ai website

    Provider account
  • Grok Bot ↗

    Grok Bot token resets, posted by the product account

    Provider account
  • Elon Musk ↗

    Grok reset announcements; high volume, so leads only

    Named source
  • SpaceXAI release notes ↗

    Model availability and quota policy; launches alone never confirm usage resets

    Provider changelog
  • Cursor changelog ↗

    Usage policy and partner quota changes

    Provider changelog
  • Gemini API changelog ↗

    API quota changes; distinguish API from consumer and Code Assist plans

    Provider changelog
  • Loic · @LDT0545 ↗

    Discovery only; no verified OpenAI affiliation

    Community lead
  • Ali · @somehowali ↗

    Discovery and user observations, never provider confirmation

    Community lead
  • Ado · @adocomplete ↗

    Verify current affiliation and first-person announcement scope for each claim

    Named source
  • OpenAI dots launch ↗

    Included dot conversations, deeper-work allowance and launch-period limits; distinguish Codex/Work usage from dot usage

    Provider product page
  • OpenAI dots help ↗

    Current plan and region eligibility, deeper-work allowance and post-launch usage terms; translated/indexed text may lag

    Provider help
  • OpenAI Pro tiers help ↗

    Pro 200 transition eligibility and dates, Pro 500 pricing and Ultrafast access; preserve unknown cutoff and timezone

    Provider help