Releases & compatibility
Antigravity Manager Updates & Compatibility
Choose stable for everyday use. Consider a preview when its release notes address a problem you can reproduce, and keep a backup so you can recover your working setup.
Stable: v5.0.0 · Published October 24, 2026
Latest preview: v5.0.2-beta.9 · Published November 2, 2026
Release list checked . Preview changes below belong to the beta channel.
Download stable v5.0.001 / Choose a release
Should I install stable or preview?
Start with stable v5.0.0 unless you need a change listed in a later preview. If your current setup works, read the changes and schedule an update when you have time to check your usual tasks.
The v5.0.0 release notes cover account scheduling, model availability, structured output, and streaming. Use your own failing task to decide which changes matter:
| Your task | What v5.0.0 changes |
|---|---|
| Keep requests moving between accounts | Introduces adaptive QoS scheduling and recovery probes. Check which account serves the request and whether a cooldown clears; use 429 and 503 troubleshooting if requests remain blocked. |
| Use an available model | Updates model ingestion when quota metadata is incomplete and filters disabled model variants. Refresh the catalog, select your model, and send a short request. |
| Get structured output | Updates Responses format/schema handling and tool conflicts. Repeat the client action that needs a structured result, such as generating a thread title. |
| Finish an agent turn | Changes stream transitions and signature handling. Test a complete tool call, its result, and the next turn in both a fresh conversation and the affected one. |
For a preview, open the exact v5.0.2-beta.9 release and choose the package for your OS and CPU. Keep the full version suffix in your notes so you can compare results with other users.
02 / Match the change to the problem
Which preview changes might help?
The latest preview is v5.0.2-beta.9. These selected changes from its release notes and the earlier tagged changelog help you find a relevant release and choose what to test after updating.
| Problem and release | Change and next check |
|---|---|
| Codex receives HTTP 200 but no output after a long thinking pause 5.0.2-beta.9 | Extends the gateway’s transition and first-byte wait for Responses streams. Repeat the affected long-context request in Codex, then check whether the tool call and final response complete. See streaming troubleshooting if it still stops. |
| Deleted accounts still receive requests 5.0.2-beta.6 | Uses the account index to control admission to the proxy pool and preserves unindexed credential files during loading. Check that a removed account disappears from rotation. Back up accounts.json together with the accounts/ directory. |
| Web or Docker OAuth gets stuck 5.0.2-beta.5 | Updates authorization-flow reuse, callback handling, and cleanup after failed exchanges. Follow the Web interface’s callback instructions, then check that the added account can serve a request. See sign-in troubleshooting. |
| User-Agent override resets after saving 5.0.2-beta.4 | Fixes persistence of that setting and updates guidance for the Hub format. Reopen the settings after saving and compare the original request. Use the detected version when following that guidance. |
| A stream ends after producing useful output 5.0.2-beta.3 | Changes how interrupted streams finish and how tool-call endings are preserved. Check the finish reason, retained output, and next tool turn with your client; use the streaming guide to identify the stage. |
| Accounts enter QoS cooldown on an unstable connection 5.0.2-beta.0–beta.1 | Adds an opt-in automatic QoS quarantine setting, followed by upload-stall and thinking-request adjustments. Review the setting and repeat the affected request. Upstream quota limits still apply. |
| IDE 2.6.0 account switching fails 5.0.1-beta.5, beta.7, beta.9 | Updates process detection and credential synchronization. Verify the active identity inside the intended IDE installation using the switching checklist. |
| Saving the update channel returns 400 5.0.1-beta.1 | Accepts the Web interface’s settings format and partial updates. Update the installation and check that the channel persists. |
Each row identifies where the change was introduced. For a current preview installation, review the intervening changes through your chosen tag and retest the same client, account, and model.
Which component needs updating?
Record three versions separately: Antigravity Manager, your Google Antigravity IDE or Classic installation, and any API client such as Claude Code or OpenCode.
- Manager: controls the local account pool, API proxy, and update settings. Find its version in Settings → About.
- IDE: has its own login state, processes, and credential storage. For switching problems, record the exact IDE version and installation path.
- API client: controls the request format and handling of streamed replies. Record its version, endpoint, and model when investigating compatibility.
Change one component at a time when diagnosing a failure. This gives you a useful before-and-after comparison and makes recovery easier.
03 / Version errors
“This version of Antigravity is no longer supported”
Check where the rejection appears, then update the component involved in that request. Keep the full message and the versions of Manager, the IDE, and the API client before making changes.
- Locate the failing route. Does the message appear in the official IDE, an API client connected to Manager, or both? Try a small request directly in the official client and through Manager with the intended account.
- Check the relevant release notes. For an IDE-only failure, check the IDE update. For the Manager route, compare Manager compatibility changes with your installed version. Follow the current release’s guidance for any User-Agent override.
- Back up and update. Use the procedure below, then repeat the original task. Read the returned content as well as the HTTP status: an HTTP 200 reply can still contain the rejection text.
- If it continues, report the comparison. Include which route works, the exact error, versions, and a short reproduction in a redacted bug report.
The older v4.2.2 report of this message remains without a confirmed solution. Use upstream-response troubleshooting for a current failure; old version strings copied from a discussion can become obsolete.
How do I change the update channel?
Open Settings → About, choose Stable or Preview (Beta) under Update Channel, then select Check for Updates. The channel selects which releases are checked; installing the offered version is a separate step.
If saving returns 400 in Web or Headless mode on v5.0.0: the Web settings request uses a format that this server rejects. The correction starts in v5.0.1-beta.1. Download an appropriate later build directly, or update your container using its pinned image, after making a backup. See desktop installation or Docker deployment.
After updating, save your channel choice, reopen Settings, and confirm it remains selected. Also check the automatic-check setting and interval. If the error persists, record the deployed version, requested channel, and status for issue #3754 or a new report.
Choosing Stable while running a beta changes the update feed. To return to an older stable binary, follow the rollback procedure.
04 / Keep your working setup
How do I update without losing my data?
Keep a protected copy of the active data directory before installing a new version, then verify your accounts, settings, and usual workflow after launch.
- Write down the working setup. Record the version, installation method, active data directory, client endpoint, and selected model. Keep the current installer or exact container image reference.
- Make a consistent backup. Save unfinished work, stop Manager and any container using the same data, then copy the complete active data directory to protected storage. Keep the account index and credential files together. The backup and restore guide explains the paths and what account export includes.
- Install the chosen version. Use the matching OS, CPU, and package format from Downloads or the exact preview release. For Docker, pull the chosen image and recreate the container with the existing volume, ports, and environment settings; follow the deployment guide.
- Confirm which copy launched. Check the displayed Manager version and data directory, especially if you keep multiple installations. Check that your accounts, model mappings, and client settings are present.
- Repeat a real task. Send a short request through your usual client. For agents, complete a tool call and a follow-up turn. For IDE switching, check the selected identity inside the IDE. Repeat the task that motivated the update and retain its result.
Keep the pre-update backup until your normal workflow has passed these checks. Account exports contain credentials: store them privately and exclude them from bug reports.
How do I return to the previous version?
Restore the previous application version together with its matching pre-update data backup, after checking the release notes for migration requirements.
- Stop Manager or the container. Save a separate copy of the failed installation’s data and the error details.
- Check whether the target version can use your backup. A newer version may have changed configuration or database formats; keep the original backup untouched.
- Reinstall the previous package, or recreate the container from its previous image reference. Restore a working copy of the matching backup using the data guide, with all processes that use it stopped.
- Start Manager and verify the version, accounts, settings, and original task. For an IDE switching problem, also check the IDE’s own session and version.
If you have no matching backup or the migration path is unclear, ask in the project’s issue tracker with both versions before opening newer data in an older build.
05 / Older installations
Where can I find a fix for an older version?
Search the changelog for the exact error or feature, then open the matching release tag and check its downloadable assets. These older cases show where to start:
Video input: request #3381 and v4.6.7
Issue #3381 tracks video blocks rejected during request parsing. If your installation predates the video-input changes, compare its tag with the changelog and update before testing. For a current build, use the media guide to select a supported request format and a small test clip.
“Stream interrupted before completion” on v4.9.2 betas
Issue #3593 includes a report that the error continued after an early proposed fix. Later versions changed stream handling again. Record your full version suffix and use the stream checklist to distinguish an upload failure, an idle timeout, and an incomplete client reply.
Missing v4.9.5 download assets
The v4.9.6 notes explain that a runner failure prevented v4.9.5 assets from being produced and that v4.9.6 republished the same code. For that historical build, open v4.9.6 and choose an actual installer from Assets. For a new installation, use the current download page.
Browse the release archive or the English changelog through v5.0.2-beta.6 for other versions.
Why do release notes only say “See the assets…”?
That placeholder can appear when the release workflow fails to match a changelog heading to the tag. Open the changelog at that exact tag to find the intended changes.
The release guide says the heading must match the full tag, including its v prefix and beta suffix. Then check the release’s Assets list for your platform. If the changelog section or package is missing, choose a release with the required information and report the missing entry.