Reported weekly Gemini quota resets for paid plansThe report links to two team-lead announcements. X returned 403 during review; report counts are not treated as reset samples.Team-lead X announcements relayed by 9to5Google
Source ↗THE RESET OBSERVATORY
When will Antigravity reset?
Review Google Antigravity quota rules and public reset reports. Its Gemini quota is separate from the Gemini app; limited evidence cannot support a forecast.
Latest collected snapshot · 2026-09-10 10:31 UTC
CodexHistory availableClaudeHistory availableGeminiUsage rulesGLMReset cardsKimiReset recordsAntigravitySeparate quota
Loading collected public records…
Antigravity reset watch
Gemini quota inside Google Antigravity, separate from Gemini web and mobile apps. Non-Gemini models also have separate limits.
Track Antigravity resets separately
Public reports link to paid-plan Gemini weekly quota resets. Official documentation confirms a shared Gemini pool inside Antigravity; this does not imply a reset in the Gemini app.
Read the official guide ↗Historical coverage is insufficient for a percentage forecast.
Evidence reviewed 2026-09-10Rule check pending or failed Sep 10, 2026, 10:31 AM UTC
Reviewed public records
1Event days usable for forecasting
0Official rule sources
0 / 1Evidence review date
2026-09-10THE RECORD
Public evidence and reset records
FOLLOW THE SIGNAL
Public sources, clearly identified.
Codex and Claude use third-party reset catalogs. Other platforms show reviewed public records and official rules. Periodic rule checks do not discover new announcements. Regular renewals, manual reset cards and policy changes are kept separate from automatic-reset forecasts.
Antigravity quota scope
StaleOfficial rules · Periodic checks, not announcement discovery
Last success Sep 10, 2026, 10:31 AM UTC
Open source ↗HOW WE ESTIMATE
An estimate,
not a promise.
Platforms can change their policies at any time. These estimates do not mean your account will receive a reset.
01Start with history, then consider new signals
Over the past 90 days, automatic reset announcements on the same UTC date count as one event day. We need at least 30 days of observation and 5 event days to show a probability. The third-party historical record may be incomplete.
The Gamma–Poisson model uses α = 1 + event days and β = 7 + observed days. The baseline probability of at least one announcement in the next h days is 1 − (β / (β + h))^α.
02How public signals affect the estimate
Reset previews, model releases, usage incidents, and community signals have manually chosen weights of 2.0, 0.35, 0.25, and 0.10. Each is scaled by source weight and decays with age. Only the past 72 hours count, and only the strongest signal in each group is used.
These weights are experimental assumptions, not trained or calibrated values. Banked resets and ordinary client updates do not increase the automatic-reset estimate. Without valid new signals, the adjusted estimate equals the baseline. The 7-day result is a longer-range extrapolation.
03How we evaluate forecasts
No probability forecasts have been issued for this platform. Usage rules, manual reset cards and relayed reports do not create forecast samples or prospective scores.
Historical replay and prospective scoring are kept separate. We need timestamped forecasts and comparisons against the baseline using Brier score and Log Loss before claiming better accuracy.
04Open-source references and event definitions
tibo-reset-watch informed public-post monitoring; tibo-reset-lab provides an auditable forecasting experiment. This site is independently implemented.
Automatic resets, banked resets that must be redeemed, and regular account usage renewals are different events. Read OpenAI’s explanation ↗