Antigravity 2.0 installer breaks existing IDE install

Google Antigravity
1

Summary

The 2.0 installer (released May 19) reuses the existing Antigravity IDE install directory. After running it, Antigravity IDE.exe no longer launches the IDE; it launches 2.0 instead. The IDE files are still on disk, just unreachable via the existing launcher.

Steps to reproduce

  1. Install Antigravity IDE 1.107.0.

  2. Run the Antigravity 2.0 installer on the same machine.

  3. Click Start Menu → Antigravity → “Antigravity IDE”, or run Antigravity IDE.exe directly.

Expected: Antigravity IDE launches. Actual: Antigravity 2.0 launches.

Directory layout after the 2.0 installer runs

%LOCALAPPDATA%\Programs\Antigravity\
├── Antigravity IDE.exe       201 MB   5/19 05:46   (IDE launcher)
├── Antigravity.exe           212 MB   5/19 17:44   (2.0 launcher)
└── resources\
    ├── app.asar              5/19 17:44            (2.0 code)
    └── app\
        └── package.json      "Antigravity IDE" 1.107.0

The IDE’s Antigravity IDE.exe and resources/app/ are untouched. The 2.0 installer added Antigravity.exe and resources/app.asar to the same directory.

Root cause

Electron exes load resources/app.asar first, then resources/app/, from the same directory as the exe. The exe name does not enter into this lookup. Because both Antigravity IDE.exe and Antigravity.exe live in the same folder, both load the same resources/app.asar (2.0). The IDE’s resources/app/ is shadowed and never reached.

The two exes therefore differ only in window title, icon, and AppUserModelID (Google.AntigravityIDE vs electron.app.Antigravity). The code that runs is whatever sits in resources/. Two separate Electron products cannot share a resources/ directory.

Confirmed by renaming app.asar aside: Antigravity IDE.exe then loaded the real IDE 1.107.0, and Antigravity.exe also fell back to the IDE folder. Both exes ran the same code.

Suggested fixes (any one resolves it)

  1. Default the 2.0 installer to a separate directory, e.g. %LOCALAPPDATA%\Programs\Antigravity2\.

  2. Detect an existing Antigravity IDE install in the target directory and either refuse to install there or prompt for a different directory.

  3. Bundle 2.0’s resources under a distinct subfolder (e.g. resources2/app.asar) and have Antigravity.exe point at it explicitly. This would let both products coexist.

Option 1 is the safest and matches the release-notes framing of 2.0 and the IDE as separate products.

Environment

  • Windows 10/11, 64-bit

  • Install dir: C:\Users\<user>\AppData\Local\Programs\Antigravity\

  • IDE: 1.107.0

  • 2.0: as released May 19, 2026

  • Installer: Inno Setup (unins000.exe present in install dir)

Current user workaround

Rename resources\app.asar aside; Antigravity IDE.exe falls back to resources\app\ and the IDE launches. Only one of the two products can be active at a time in this state.

5 Likes