antigravity-preview-05-2026 has shut down: here is what you need to do now
Google's antigravity-preview-05-2026 agent harness reached its hard shutdown on 5 October 2026. All API calls must now target antigravity-preview-09-2026.
If your application calls the Gemini API using the string antigravity-preview-05-2026, it is failing right now. Google’s hard shutdown date for that agent harness version was 5 October 2026, and there is no grace period, no fallback, and no automatic redirect. Every API call, scheduled workflow, or CI pipeline still pointing at the old version string returns a “version no longer supported” error.
The replacement, antigravity-preview-09-2026, has been available since 17 September 2026. If you have not migrated yet, that is the only thing on your to-do list.
What happened and when
Google launched antigravity-preview-05-2026 on 19 May 2026 alongside the Antigravity 2.0 announcement at Google I/O. It introduced a general-purpose managed agent on the Gemini API, capable of reasoning, executing code, managing files, and browsing the web inside a secure Linux sandbox, all from a single API call. The default model was Gemini 3.8 Flash, configurable down to Gemini 3.5 Flash-Lite.
On 17 September 2026, Google shipped antigravity-preview-09-2026 and marked the May version as deprecated, with the official deprecations page giving a firm end date of 5 October 2026. That date has now passed.
What the new version changes
For many teams, the migration is a one-line change: swap antigravity-preview-05-2026 for antigravity-preview-09-2026 in your agent configuration. If you are running the agent on a remote sandbox and only reading its output text or model_output steps, that is genuinely all you need to do.
If your integration goes deeper, there are two breaking changes to address.
PascalCase parameters. Every built-in tool parameter has been renamed from snake_case to PascalCase. For example, file_path is now FilePath. If you are parsing function_call steps directly or passing parameters to built-in tools, you will need to update those references.
Line-range file editing. The September harness replaces full-file rewrites with line-range replacements. This is faster and cheaper on tokens, but if your code assumes it will receive a complete file back from an edit operation, it will break.
Beyond the breaking changes, the new version also brings two additions worth noting: find_by_name() and grep_search(), a pair of new built-in tools for file and code search that were not available in the May version.
New APIs bundled with the update
antigravity-preview-09-2026 ships alongside two new APIs that extend what the managed agent can do.
The Files API brings the Antigravity Coding Agent’s file-handling behaviour directly into the Gemini API surface.
The Credentials API lets you store a credential server-side under an ID and reference it from an allowlist rule, rather than freezing a header value into an interaction at submit time. The proxy resolves the credential per request, which makes rotating secrets significantly cleaner in practice.
Both are available now in AI Studio and the Interactions API.
What you should check before anything else
Run a search across your codebase, configuration files, environment variables, and CI definitions for the string antigravity-preview-05-2026. It is easy to miss one place, particularly in scheduled jobs or infrastructure-as-code templates that do not surface in normal test runs.
Once you have found every reference, the decision tree is straightforward:
- Running on remote sandbox, reading output text only: update the string, deploy, done.
- Running tools locally or parsing
function_callsteps: update the string, update parameter names to PascalCase, update any file-edit handling for line-range replacements, then test.
The official changelog and the antigravity-preview-09-2026 model documentation have the full parameter reference if you need to cross-check specific tool signatures.
A note on what is still not there
The September update does not close every gap. Three tools remain unavailable in the managed agent harness: file_search, computer_use, and google_maps. If your May implementation worked around their absence, nothing changes on that front in the September version.
The bottom line
There is no version of antigravity-preview-05-2026 that still works from 5 October 2026 onwards. The migration path is well-documented, the replacement has been stable since mid-September, and for most integrations the effort is small. The main risk at this point is simply not having done it yet.