Use Google Antigravity IDE as your Unity script editor, with proper IntelliSense, project file generation and single-instance window reuse.
Heads up: Google split the Antigravity product line at I/O 2026 (May 19, 2026).
There are now two desktop apps that look similar but do very different things —
the standalone Antigravity is an agent-orchestration tool with no code
editor inside it, and Antigravity IDE is the VS Code fork you actually
want for writing C#. Older versions of this package (and most of the
community forks I found) matched any Antigravity*.exe, which means Unity
ended up opening the agent app every time you double-clicked a script.
v1.0.6+ fixes that — see Antigravity 2.0 split for
the full story.
If this saved you an afternoon of "why is the agent app opening my scripts?", please ⭐ the repo. That's how other Unity devs find it.
- Auto-Discovery: automatically finds your Antigravity IDE installation on macOS, Windows and Linux (and ignores the standalone Antigravity agent app, which cannot host script editing).
- IntelliSense: generates
.slnand.csprojfiles for complete C# IntelliSense and Unity API support inside Antigravity IDE. - Workspace Setup: writes
.vscode/workspace config files (launch.json,settings.json,extensions.json) that Antigravity IDE reads as a VS Code fork. - Reuse Window: optional setting to open files in an already-running
Antigravity IDE window instead of launching a new one. Backed by a scan of
Antigravity IDE's own
workspaceStoragedirectory. - Insider builds supported:
Antigravity IDE - Insider/antigravity-ide-insidersare discovered on all three platforms.
Install via Unity Package Manager using the git URL:
- Open
Window > Package Manager - Click
+→ Add package from git URL... - Enter:
https://github.com/BadranRaza/com.unity.ide.antigravity.git - Click Add
The package will appear in Package Manager under the name
com.badranraza.ide.antigravity and can be updated from there when new
versions are released.
Alternative: if you cloned the repo locally, use
+ → Add package from disk...and point to thepackage.json.
Upgrading from v1.x? v2.0.0 renamed the UPM
namefield fromcom.unity.ide.antigravitytocom.badranraza.ide.antigravity(the old name used Unity's reservedcom.unity.*namespace and was rejected by OpenUPM). To upgrade: in Package Manager, remove the oldcom.unity.ide.antigravityentry and re-add via the same git URL above. Your External Tools selection survives the rename. The GitHub repo URL is unchanged.
- Install Antigravity IDE from antigravity.google.
- Go to
Unity > Preferences > External Tools(macOS) orEdit > Preferences > External Tools(Windows / Linux). - Select Antigravity IDE from the External Script Editor dropdown. If you previously had a plain "Antigravity" entry selected, that was the agent app — pick "Antigravity IDE" instead.
- Choose which package types should have
.csprojfiles generated. - Click Regenerate project files to apply.
When Antigravity IDE is selected as the editor, a "Reuse existing Antigravity window" toggle appears in Preferences. When enabled, double-clicking a script in Unity will open it in an already-running Antigravity IDE instance instead of launching a new one.
At Google I/O 2026 (May 19, 2026) Google split the Antigravity product line into two separate desktop applications:
| Product | What it is | Default install dir (Windows) | Process / exe name |
|---|---|---|---|
| Antigravity (2.0) | Agent-first standalone desktop app. Multi-agent orchestration UI. Not a code editor. | …\Programs\Antigravity\Antigravity.exe |
Antigravity.exe |
| Antigravity IDE | VS Code fork. The actual code editor. This is what Unity needs. | …\Programs\Antigravity IDE\Antigravity IDE.exe |
Antigravity IDE.exe |
Both share the same Code-fork shell. They are told apart by
resources/app/package.json name field ("Antigravity" vs
"Antigravity IDE"), which this package verifies during discovery. Older
versions of this package (≤ 1.0.5) matched any Antigravity*.exe, which on
machines with both products installed could route Unity script opens into the
agent app. Starting in v1.0.6, only Antigravity IDE installs are listed.
- Workspace config is written to
.vscode/in your Unity project root — Antigravity IDE reads these as a VS Code fork. - Extensions are looked up from
~/.antigravity-ide/extensions/(~/.antigravity-ide-insiders/extensions/for insider builds) — Antigravity IDE's user-level extension directory. - Window reuse works by reading Antigravity IDE's
workspaceStoragedirectory to find which workspace a running instance has open:- Windows:
%APPDATA%\Antigravity IDE\User\workspaceStorage - macOS:
~/Library/Application Support/Antigravity IDE/User/workspaceStorage - Linux:
~/.config/Antigravity IDE/User/workspaceStorage
- Windows:
- Unity 2019.4 or later
- Antigravity IDE installed from antigravity.google (the standalone Antigravity 2.0 agent app does not work as a Unity script editor)
This was the whole reason v1.0.6 exists. Update the package to v1.0.7 or
later, then in Edit > Preferences > External Tools re-select Antigravity
IDE from the dropdown (your old saved preference might still point at the
agent app's executable; re-picking fixes it).
If you've also got the standalone Antigravity 2.0 agent app installed and
want to make absolutely sure it can't be picked: the detection now reads
resources/app/package.json inside each install and rejects anything whose
product name isn't exactly Antigravity IDE. You don't have to uninstall
the agent app for the IDE to work.
Three things to check:
- You've actually installed Antigravity IDE, not just the agent app.
Grab the IDE installer from antigravity.google.
On Windows it lands in
%LOCALAPPDATA%\Programs\Antigravity IDE\Antigravity IDE.exeby default, on macOS in/Applications/Antigravity IDE.app, on Linux at/usr/bin/antigravity-ide(or the XDG.desktopentry). - The package actually imported. Open
Window > Package Manager, switch the filter to "In Project", confirm Antigravity IDE Editor is listed at v1.0.7 or newer. - Unity needs a domain reload after installing the package. Closing and reopening Unity is the surefire way; toggling Play mode usually works too.
If it still doesn't show up, click Browse in External Tools and point
manually at Antigravity IDE.exe (Windows), Antigravity IDE.app (macOS) or
the antigravity-ide binary (Linux). The discovery code will accept it as
long as the manifest's product name is Antigravity IDE.
Antigravity IDE is a VS Code fork, so the same constraints apply: Microsoft's
official C# / C# Dev Kit / Unity extensions are licensed only for Visual
Studio Code itself, not for forks. The community-recommended replacement is
DotRush (open-source Roslyn-based C# language server) — install it from
the Extensions panel inside Antigravity IDE, then make sure the .sln
generated by this package is at the workspace root.
The recommendations file this package writes (.vscode/extensions.json)
suggests visualstudiotoolsforunity.vstuc, which is the standard pointer
used by the upstream com.unity.ide.vscode package this is forked from. On
Antigravity IDE specifically, swap to DotRush.
The toggle reads Antigravity IDE's own workspaceStorage directory
(%APPDATA%\Antigravity IDE\User\workspaceStorage on Windows, the equivalent
on macOS / Linux) and matches each running Antigravity IDE process by the
workspace path stored there. If you've never opened the Unity project in
Antigravity IDE before, there's nothing to match — open it once normally,
then the toggle starts working.
If you previously used the older Antigravity 1.x and have data in the
legacy \Roaming\Antigravity\User\workspaceStorage, v1.0.6+ no longer reads
it (that path now belongs to the agent app). Either re-open your project
once in Antigravity IDE, or copy the relevant workspaceStorage subfolder
across manually.
Insider builds (Antigravity IDE - Insider.exe, antigravity-ide-insiders,
Antigravity IDE - Insider*.app) are detected starting in v1.0.7. If you're
on the insider channel and it doesn't show up, make sure the package is at
v1.0.7 or newer, then re-open Unity to force a domain reload.
There are several community packages that all try to do the same thing. Here's where they sit as of May 2026, in case you're choosing:
| Fork | Last push | Stars | Antigravity 2.0 fix? |
|---|---|---|---|
| BadranRaza/com.unity.ide.antigravity (this one) | 2026-05-23 | live | ✅ v1.0.6+ — full detection + manifest check |
| alexakajustin/Antigravity-Unity | 2026-05-20 | 1 | /Antigravity.exe |
| billythekidz/UnityAntigravityIDE | 2026-03-21 | 15 | ❌ predates the split |
| usmanbutt-dev/antigravity-unity | 2026-02-09 | 21 | ❌ predates the split |
| akshwpsh/com.unity.ide.antigravity | 2026-02-25 | 3 | ❌ predates the split |
| TermWay/unity-ide-antigravity | 2025-11-30 | 21 | ❌ predates the split |
| kientux/com.unity.ide.antigravity | 2025-12-12 | 0 | ❌ predates the split |
If you're already on one of those and it's working for you, you don't have to switch. If Unity is opening the agent app on every script double-click, this is what fixed it for me.
If this package made your Unity + Antigravity IDE setup work:
- ⭐ Star the repository — biggest single thing you can do to help others find it.
- 🔁 Share the repo link with other Unity devs who use Antigravity IDE.
- 💬 Open an issue or discussion if you hit a bug or have a feature request.
- 🔧 Pull requests welcome — see open issues for ideas.
MIT. Free to use in personal, commercial and Asset Store
projects. Includes upstream MIT-licensed code from Unity Technologies and
Microsoft Corporation (the com.unity.ide.vscode package this is forked
from).
Maintained by Badran Raza (@BadranRaza) —
Unity / game-side software developer based in Lahore, Pakistan. If you've
hit a bug or want to contribute, the Issues
and Discussions
tabs are the right entry points. For the story of why this package exists
and how the Antigravity IDE detection works under the hood, see
Documentation~/antigravity-2-0-fix.md.