Google announces an Argon and Gemini reset in Antigravity

Google has announced a reset of Argon and Gemini model allotments in Antigravity. The notice appeared on October 16, 2026 at 2226 UTC, giving developers who had used their allowance a reason to check their available capacity again.

The original announcement comes from Rody Davis through his verified Googler account. It describes a reset for everyone in Antigravity. That establishes the announced scope, but does not establish when the change finished reaching every account. The practical next step is to inspect your own balance before resuming a long task.

Argon and Gemini have separate allowance buckets

In a reply to the announcement, Davis says Argon and Gemini use different buckets. This matters when one model stops accepting work while another still has capacity. A remaining Gemini allowance should not be treated as a reliable reading of the Argon allowance.

The notice does not specify a new permanent quota, a guaranteed number of prompts or a deadline for using the reset. It also does not promise that unused allowance accumulates or that the next scheduled refresh stays unchanged. Those details should not be inferred from the word reset.

Check the account before restarting a large job

For Antigravity CLI users, the most direct check is /usage, with /quota available as an alias. Google’s command documentation says opening this panel refreshes model configuration and quota status from the backend. It displays model allowances and supports scrolling through entries. Refreshing this view retrieves the current status. It does not itself grant another reset.

Before continuing work, note the selected model, its displayed allowance and any refresh time shown by your account. If the interface does not clearly distinguish Argon from the other Gemini models, avoid assuming that one combined looking indicator describes both pools. Keep the exact model name and a screenshot of the status if you need to explain a mismatch to support.

A sensible way to resume is with a bounded piece of unfinished work. Ask the agent to identify the last completed step, review the changes already made and continue with one clear acceptance check. This is workflow advice rather than a claim that ByteForward tested the reset. It reduces the chance of spending newly available capacity repeating work that is already complete.

A reset does not change model eligibility

Google’s current model table lists Argon for paid Google AI Pro subscriptions outside trials, Ultra and Enterprise. It lists availability in the Antigravity App, CLI and IDE extensions, while excluding the standalone Antigravity IDE. A reset of an allowance therefore should not be read as a promise to unlock Argon on every plan or surface.

If Argon is absent from the model picker, first check the product and subscription eligibility rather than treating it as an exhausted quota. Our paid Pro access guide explains the separate weekly Argon notice and the distinction between the app and standalone IDE.

Watch the normal limits and credit settings

Google’s plans documentation says quota consumption reflects the work an agent performs, so a complex task can consume more allowance than a straightforward request. The general Pro plan has a five hour refresh subject to a weekly ceiling. That general cadence should not be substituted for a more specific Argon allowance shown in your account.

The same documentation describes AI Credit Overages for eligible Pro and Ultra users. The Never option waits for baseline quota to refresh. The Always option permits eligible AI credits to be used after the baseline is exhausted. Review that setting before assuming continued work is using only the reset allowance. The announcement does not separately explain credit behavior for this event.

For planning purposes, treat the reset as an opportunity to inspect available capacity and finish useful work. Keep any longer project schedule tied to the limits your account actually displays. ByteForward’s reset history records the announcement date so it can be distinguished from later resets.

Illustrative coding workspace. Photo by Dawit on Unsplash, used under the Unsplash License.