Google Antigravity release notes: 2.12 adds quoting, /boost, and Gemini 3.8 Flash

Google Antigravity 2.12.0, dated September 2, 2026, lets you highlight part of an Antigravity response and quote it as context in the next prompt. Paid users also get /boost, a slash command that increases thinking effort through a multi-agent reasoning pipeline.

Source: Google Antigravity 2.12.0 release notes.

What the Google Antigravity 2.12 release notes change

Highlight the part of a response you want to continue with and quote it as context in a precise follow-up question. You do not need to refer to the entire answer.

/boost is available to paid users. Google describes it as higher thinking effort through a multi-agent reasoning pipeline. The release notes do not specify limits or explain how the models divide the work.

Version 2.12.0 also shows which projects override a general setting and links directly to each project's settings. Split terminal layouts now persist across window reloads.

Source: Google Antigravity 2.12.0 changelog.

Gemini 3.8 Flash in AGY Enterprise

Google Antigravity 2.12.2, dated September 3, makes Gemini 3.8 Flash selectable for AGY Enterprise users through ADC. ADC stands for Application Default Credentials, Google Cloud's search order for credentials in the environment where an application runs.

Google says the model can be used for agentic tasks. The release notes do not document a separate activation path beyond Enterprise and ADC, so check the model selector in your environment once the version reaches your installation. Google notes that new Antigravity versions roll out gradually and may take a few days to reach everyone.

Sources: Google Antigravity 2.12.2 release notes. How Application Default Credentials works.

Short example: use the new Antigravity feature

Human step: Once 2.12.0 is available in your installation, highlight the relevant part of an Antigravity response and add it as a quote in your follow-up. Then paste the prompt below the quote.

Review the quoted part of the plan. Find one unsupported claim and one dependency that needs verification. Suggest one concrete correction. Do not edit files.

Good output should:

• Refer to the quoted passage rather than the rest of the conversation.
• Separate an unsupported claim from a technical dependency.
• Suggest a bounded correction without editing files.