Hi! I'm the maintainer of BadranRaza/com.unity.ide.antigravity, one of the other community Antigravity-Unity packages. Filing this as a heads-up rather than a bug report — feel free to close as wontfix if it doesn't fit your roadmap.
What changed
At Google I/O 2026 (May 19, 2026) Google split the Antigravity product line into two separate desktop apps:
| Product |
What it is |
Default Windows path |
| Antigravity (2.0) |
Agent-orchestration tool. No code editor. |
%LOCALAPPDATA%\Programs\Antigravity\Antigravity.exe |
| Antigravity IDE |
VS Code fork. The actual code editor. |
%LOCALAPPDATA%\Programs\Antigravity IDE\Antigravity IDE.exe |
Both share the same Code-fork shell, so the standard discovery regex (*Antigravity*.exe) matches both. On machines with both installed, Unity often ends up launching the agent app on every script double-click — and the agent app has no editor surface, so users just stare at the agent home screen instead of their script.
How I fixed it in my fork (in case it's useful)
Three layers:
-
Filename filter — discovery only accepts Antigravity IDE.exe / Antigravity IDE*.app / antigravity-ide[-insiders].
-
Manifest verification — read resources/app/package.json and reject anything whose name field isn't Antigravity IDE. This is defence-in-depth if a user manually Browse...-es to the agent app.
var manifest = JsonUtility.FromJson<VisualStudioCodeManifest>(File.ReadAllText(manifestFullPath));
manifestName = manifest.name;
// …
if (!string.IsNullOrEmpty(manifestName) &&
manifestName.IndexOf("Antigravity IDE", StringComparison.OrdinalIgnoreCase) < 0)
return false;
-
Search-path narrowing — drop the bare Antigravity install dirs from the candidate list entirely.
Process matching for "reuse existing window" features and workspace-storage paths also need updating — AppData/Application Support/.config now use Antigravity IDE subfolders, not Antigravity.
Full write-up with code refs: https://github.com/BadranRaza/com.unity.ide.antigravity/blob/master/Documentation~/antigravity-2-0-fix.md
If you'd rather link to my package than port the change, the README in this fork mentions the trade-offs, but honestly either approach is fine — the goal is just to get fewer Unity devs stuck staring at the agent app's home screen. 🙂
— Badran
Hi! I'm the maintainer of BadranRaza/com.unity.ide.antigravity, one of the other community Antigravity-Unity packages. Filing this as a heads-up rather than a bug report — feel free to close as
wontfixif it doesn't fit your roadmap.What changed
At Google I/O 2026 (May 19, 2026) Google split the Antigravity product line into two separate desktop apps:
%LOCALAPPDATA%\Programs\Antigravity\Antigravity.exe%LOCALAPPDATA%\Programs\Antigravity IDE\Antigravity IDE.exeBoth share the same Code-fork shell, so the standard discovery regex (
*Antigravity*.exe) matches both. On machines with both installed, Unity often ends up launching the agent app on every script double-click — and the agent app has no editor surface, so users just stare at the agent home screen instead of their script.How I fixed it in my fork (in case it's useful)
Three layers:
Filename filter — discovery only accepts
Antigravity IDE.exe/Antigravity IDE*.app/antigravity-ide[-insiders].Manifest verification — read
resources/app/package.jsonand reject anything whosenamefield isn'tAntigravity IDE. This is defence-in-depth if a user manuallyBrowse...-es to the agent app.Search-path narrowing — drop the bare
Antigravityinstall dirs from the candidate list entirely.Process matching for "reuse existing window" features and workspace-storage paths also need updating — AppData/Application Support/.config now use
Antigravity IDEsubfolders, notAntigravity.Full write-up with code refs: https://github.com/BadranRaza/com.unity.ide.antigravity/blob/master/Documentation~/antigravity-2-0-fix.md
If you'd rather link to my package than port the change, the README in this fork mentions the trade-offs, but honestly either approach is fine — the goal is just to get fewer Unity devs stuck staring at the agent app's home screen. 🙂
— Badran