What goes into the archive

This archive records public Gemini quota resets on Google Antigravity and related reset notices from Varun Mohan. Each row links to the announcement and states the model scope that the source actually names. The archive covers the posts reviewed for this site. A missing date means there is no entry here for that date. It cannot establish whether a reset happened privately, applied only to some accounts, or appeared in a post we have not located.

We record a dated announcement when it says a reset has occurred or is being carried out. A post promising a reset later can explain the timing, but we use the later confirmation when we can match both posts to the same event. Replies, reposts, and notices that repeat the same reset do not create additional events. If a post changes after we record it, we compare it with the source again and correct the entry when the available evidence supports a change.

How we label the scope

  • Gemini only means the original announcement specifically names Gemini. It does not establish a reset for every other model on Antigravity.
  • Gemini + Argon means the announcement names both. The November 6 and October 16 entries illustrate this wording.
  • All models means the announcement indicates all models. The November 17 anniversary entry is one recorded example.
  • Model not specified covers posts that mention a reset without naming a model. This includes a post that describes a weekly quota reset without identifying a model group. Its table row preserves that more specific wording.

The scope and audience are different. “All users” describes who was included. “All models” describes what was reset. A post can announce a Gemini reset for everyone without saying all models were included. When the scope is unclear, open the original post rather than treating a broad phrase in one announcement as proof of broader coverage.

How the dates and counts work

The main table groups entries by UTC month. Select local time to convert the publication timestamps to your browser’s time zone. The month group stays in UTC, so an entry near midnight can show a different local date. For example, a post published late on November 17 in UTC can fall on November 18 in parts of Asia. The publication time is evidence of when the source posted, not when a particular account received a refill.

The totals count entries in the archive. Each entry contributes to one scope category. The average interval uses the differences between consecutive publication timestamps, and the longest gap uses the largest of those differences. Both are rounded for display. These describe the reviewed record and give no timetable for future announcements. A long gap could reflect a period without a recorded public reset or a gap in the sources reviewed.

How to check a row against your account

Start with the original post and check its model and audience wording. Then open your Antigravity usage panel for the same account and model group. An account’s normal refill can happen between public announcements. A short-window refill can also make an account usable again without any public announcement. See how to check your own Gemini reset time in Settings or the CLI. Official Antigravity plan documentation

Report a missing or incorrect entry

If you find an overlooked public reset, a wrong timestamp, or a source that no longer matches its row, send the original post link, the date you noticed, and the text that needs review to hello@gemini-reset.com. An original public source makes it possible to compare wording and identify duplicates. Please leave account credentials and private usage screenshots out of the message. The latest Gemini reset announcement is the quickest place to see the most recent record.