The evidence behind the headline
Watch the source.
Provider posts, replies and community leads. Every signal keeps its provenance and its unanswered questions.
Latest linked-source review: . Twenty-five linked originals rechecked without changed terms. All 13 recent-post discovery feeds responded after SpaceXAI recovered from a transient HTTP 404 response. Tibo's verified Day 2 roundup lists four numbered improvements: free Auto-review, simplified API access for builders, integrated meeting notes and a live Decisions API for builders. None is described as a reset. Loic's reset request is community commentary; Grok Bot's usage-credit reply is a support action rather than a reset announcement. OpenAI's large-PDF Responses API incident resolved without a reset remedy. No other new reset evidence appeared in bounded feeds or provider pages; public Tibo timeline remained HTTP 429, OpenAI pages remained inaccessible and the Cursor checker retained its known URL parsing failure. The 28-day reset signal stays Developing: Day 2 shipped four improvements, while full resets remain possible on later days but unpromised. The earlier Pro 500 investigation and promised 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
28 days of improvements—or possible full resets.
Developing · Day 2 delivered four usage and workflow improvements: free Auto-review, simpler API tiers, integrated meeting notes and a Decisions API. No verified wording describes any as a reset. Keep the reset signal at watch because full resets remain possible on later days but no reset date, eligibility, mechanics, count or delivery is promised.
“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.
Still missing: Whether any full reset will occur · Reset dates and timezone · Eligibility, mechanics and affected usage windows
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 ↗Primary statements
Posts, replies and quoted-post context; explicit reset verbs, timing and scope
- OpenAI ↗Provider account
Launches, quota changes and reset announcements
- OpenAI Developers ↗Provider account
Codex announcements and replies
- OpenAI status ↗Provider status
Quota incidents and recovery; recovery alone does not prove a reset
- Claude ↗Provider account
Model launches and launch-day limit offers; check full threads, resets often sit in a reply
- Claude Developers ↗Provider account
Claude Code limits, banked credits and Max resets
- Anthropic ↗Provider account
Plan changes, launch offers and explicit resets
- Lydia Hallie ↗Named source
Claude Code statements; verify current role and exact scope
- Claude status ↗Provider status
Usage-limit incidents and remedies
- SpaceXAI · xAI ↗Provider account
Grok releases and quota announcements; account linked from the official x.ai website
- Grok Bot ↗Provider account
Grok Bot token resets, posted by the product account
- Elon Musk ↗Named source
Grok reset announcements; high volume, so leads only
- SpaceXAI release notes ↗Provider changelog
Model availability and quota policy; launches alone never confirm usage resets
- Cursor changelog ↗Provider changelog
Usage policy and partner quota changes
- Gemini API changelog ↗Provider changelog
API quota changes; distinguish API from consumer and Code Assist plans
- Loic · @LDT0545 ↗Community lead
Discovery only; no verified OpenAI affiliation
- Ali · @somehowali ↗Community lead
Discovery and user observations, never provider confirmation
- Ado · @adocomplete ↗Named source
Verify current affiliation and first-person announcement scope for each claim
- OpenAI dots launch ↗Provider product page
Included dot conversations, deeper-work allowance and launch-period limits; distinguish Codex/Work usage from dot usage
- OpenAI dots help ↗Provider help
Current plan and region eligibility, deeper-work allowance and post-launch usage terms; translated/indexed text may lag
- OpenAI Pro tiers help ↗Provider help
Pro 200 transition eligibility and dates, Pro 500 pricing and Ultrafast access; preserve unknown cutoff and timezone