How can I install the Antigravity application system-wide instead of installing it only for the current user? VSCode provides a separate installer that allows installation as a system-wide application, but I can’t find a similar installer for Antigravity.
Hello,
Thank you for your addressing the query regarding a system-wide installer for Antigravity and please be assured that I have shared your feedback with our internal team for further review.
We appreciate your continued patience as we work to enhance the Antigravity experience.
Here is the current status and official guidance:
Current Installer Type: The current Windows .exe is a User-Level installer , which installs by default to the user’s local AppData folder as noted in the Official Installation Guide.
System-Wide Availability: There is currently no official MSI or System Installer available for a single machine-wide installation.
Multi-User Workaround: To provide access to multiple users on the same PC, you must run the Official Download while logged into each individual Windows account.
Requirements for All Users: Regardless of the installation method, each user must be 18 or older and complete the Google Age Verification to unlock the generative AI features within the IDE.
This is actually quite an issue for me as any local installations get removed reguarly so I have to keep reinsitalling antigravity. With VS Code I just user the system installer.
Do you have any ETA for the system-wide installation? This is something we’re eagerly waiting for, since a per-user installation model is very difficult to work with in a non-persistent VDI environment.
This is a recurring problem with Google. Google makes all of its software per-user installable which VIOLATES most businesses’ security policies that forbit per-user installs. Per-user installs are much more difficult to manage using a RMM system and limits admins’ ability to police installed software. I routinely find Chrome installed for example. Sorry to break it to you, but the days of Chrome on every system are gone. Google needs to adopt a REAL security policy that provides for system-wide installs for all its installable apps.
The antigravity 2.0 and the IDE still does not have the system wide or System Installer available. Any news on it?
To add to Terabyte’s excellent point, the lack of a system-wide installer is a massive blocker for enterprise environments because of AppLocker.
When software installs to AppData\Local, it directly conflicts with standard security frameworks. In a secure corporate environment, standard users are strictly forbidden from executing binaries from their user profile paths. While we could theoretically bypass this by creating AppLocker path rules, doing so is completely against security best practices as it opens up massive holes for malware. Frankly, I would also rather not resort to creating publisher rules for an entire environment just to accommodate one tool, when Google could just do it right from the start.
If Google wants Antigravity to be adopted by developers in corporate, government, or enterprise environments, a proper machine-wide MSI installer that deploys to Program Files is an absolute necessity. Relying on per-user AppData installations simply doesn’t align with modern endpoint security best practices.
Run the installer as admin and click the browse button when setting the installation path. Then, navigate to your Program Files directory. The program will whine at you for running it as admin but you can just ignore that. Installing it this way installs it as a system-wide installation allowing it to run in Administrator mode instead of User mode. This way even the update engine will actually work instead of being blocked.
Keep in mind that this method only works for the Antigravity IDE. The Antigravity CLI has no system-wide installation method at this time.
For system-wide installations of the Antigravity CLI, you would need admin permissions on the system you are installing it to and the know-how to manually move it to an admin location after installing it. Naturally, this would also involve editing registry entrees to ensure everything is pointing to the new location.
