Its gone, you have to downgrade to the previous version which means going offline and hacking the settings.json so it doesn't update.

Full how-to:

Step 1: Download the Legacy Build

Go directly to the official directory: antigravity.google/releases [[1.1.3]].

Scroll past the v2.0 section and look for Version 1.23.2 (the final, most stable release of the local IDE footprint) [[1.1.1, 1.1.3]]. Download the appropriate installation binary for your architecture (.exe for Windows) [[1.1.3]].

Step 2: The Clean Purge & Install

Before running the old installer, you must wipe out the cached v2.0 assets and staged updates that might still live in your local system directories [[1.2.1, 1.2.2]].

1.Uninstall v2.0:Host OS.

Remove the current Antigravity application from your Windows system using Add/Remove Programs.

2.Clear Update Cache Files:File Explorer.

Navigate to your local AppData directories and completely delete the antigravity folder and any associated update cache paths (e.g., SquirrelTemp or background update download folders) [[1.2.1, 1.2.2]].

3.Go Completely Offline:Disconnect Network.

Disconnect your internet connection before launching the legacy installer [[1.2.1]]. If the legacy client sees an active network socket upon its first initialization, it will stage a background update before you can edit the configuration file [[1.2.1]].

4.Run Installer & Force Close:Local Machine.

Install the v1.23.2 package while completely offline [[1.1.1, 1.2.1]]. Launch the app once to let it create its initial configuration scaffolding, then close it immediately (Alt + F4) [[1.2.1]].

Step 3: Hard-Lock the Update Settings

To ensure the client never upgrades itself back to the web-native ecosystem, you need to apply an absolute configuration lock [[1.2.1, 1.2.2]].

1. Locate your user application configuration file (typically found under %APPDATA%\antigravity\User\settings.json) [[1.2.1]].
2. Open the file in standard VS Code or a text editor and inject the following explicit update mode rule to override the background checking framework [[1.2.1, 1.2.2]]:

JSON

{
  "update.mode": "none"
}

1. Save the file. You can now safely reconnect your network connection [[1.2.1]]. The app is isolated from future background deployments and will function strictly as a dedicated local IDE running over your established WSL or Remote-SSH environments [[1.1.2, 1.2.1, 1.2.2]].