Antigravity 2.0 Install on Linux

The current ways to install Antigravity 2.0 on Linux are astonishingly bad.

I refuse to install things via curl | sh paths. Because I don’t know what a random internet shell script is doing, I don’t want to use this as a general install path. It may be ok for one or two things, but everyone is doing this now, and it’s ridiculous. If I want to clean things up, uninstall, etc, I don’t want to have to start a research project to find out what the original install script might have done to my system years ago to revert it all.

Installing 2.0, therefore, is generally just a tarball. Immediately out of the gate, it can’t authenticate via oauth easily, because a binary in an unpacked tarball in a random location on my machine, weirdly, is not registered to handle OAuth URL callbacks.

Can we at least get a supported Flatpak release, or .deb repository path for installing/updating Antigravity, so that I don’t have to rely on magic under the hood?

There also doesn’t appear to be any supported way on installing Antigravity CLI except via shell script.

Because of this same problem, I created a script to automate the installation:

It even creates an icon for easier access.

Here is a single command community solution:

INSTALLER_URL="https://opensnap.github.io/antigravity/install.sh"
curl -fsSL "$INSTALLER_URL" | sudo -E env ANTIGRAVITY_LINUX_INSTALLER_URL="$INSTALLER_URL" bash -s -- --all

It installs both the Antigravity 2.0 and the IDE smoothly like native apps.
Learn more: Antigravity Linux Installer — One-command setup for Google Antigravity 2.0 on Linux

These are both just doing the exact thing that I don’t want to do. I want a standardized, defined install/uninstall path, which you get with Flatpak or .deb.

This helper gives you a defined install and uninstall path, but it is not a Flatpak or .deb package.
See: https://opensnap.github.io/antigravity/#paths

You are completely missing the point Elliot is making. It’s not just putting a pretty wrapper around installing the tarball.

You’re absolutely right! In fact, google knew this when they made these deb and rpm repositories. They just chose to start doing a worse job.

And yes, I am perfectly capable of installing from .tar.gz, but it’s messy and hard to maintain over time.