Antigravity 2.0 and the Antigravity IDE currently ship for Linux as raw
.tar.gz archives — no .deb, no .AppImage, no Flatpak, no installer.
This gist is a small set of shell scripts that turn one of those extracted
tarballs into a proper user-local install: a desktop launcher in your app
menu, a CLI symlink on your $PATH, an icon, and (on Ubuntu 24.04+) a
working Chromium sandbox via an AppArmor profile.
Status: community workaround. Replace with whatever Google ships officially when they get around to it.
- App installed to
~/Applications/<app>/(user-owned — no sudo needed for the app itself or for future updates). - Launcher in
~/.local/share/applications/so it shows up in the app menu, taskbar, etc. - Icon in
~/.local/share/icons/hicolor/512x512/apps/. - Symlink in
~/.local/bin/soantigravity/antigravity-idework from the terminal (this dir is on$PATHby default on Ubuntu). - For the IDE, the desktop integrations VS Code's
.debwould normally set up:- "Open With → Antigravity IDE" on folders and text files in the file
manager (via the
.desktopMimeType=field). - "Open in Antigravity IDE" as a top-level right-click entry in
Nautilus (GNOME Files). This needs
python3-nautilus; the installer offers to apt-install it for you. antigravity-ide://URL scheme registered as the default handler, so deep links open the IDE.
- "Open With → Antigravity IDE" on folders and text files in the file
manager (via the
Ubuntu 24.04+ ships with kernel.apparmor_restrict_unprivileged_userns=1,
which blocks Chromium's user-namespace sandbox for any unsigned binary
without a matching AppArmor profile. The install scripts handle this by
dropping a tiny per-binary profile in /etc/apparmor.d/ that allows
userns for exactly the installed binary path. This step needs sudo —
once. Updates afterwards do not need sudo, since the binary path
doesn't change.
If sudo fails or you decline, the script falls back to writing
--no-sandbox into the launcher's Exec= line. The app still runs, just
without renderer sandboxing. Your call.
Extract the tarball wherever, then point the matching install script at
the extraction directory. The script moves the extracted directory into
~/Applications, so the source path won't exist afterward.
# Antigravity (the 2.0 "Hub" app)
tar xzf Antigravity.tar.gz
./install-antigravity.sh ./Antigravity-x64
# Antigravity IDE
tar xzf "Antigravity IDE.tar.gz"
./install-antigravity-ide.sh "./Antigravity IDE"After install, launch from your app menu or:
antigravity # the Hub
antigravity-ide # the IDEIf the CLI doesn't resolve, make sure ~/.local/bin is on your $PATH
(it is by default on Ubuntu after a fresh login).
When a new tarball drops, just re-run the install script with the new
extraction. It replaces ~/Applications/<app>/ in place, leaves your
settings and the AppArmor profile untouched, and refreshes the icon /
desktop entry.
tar xzf Antigravity.tar.gz # latest
./install-antigravity.sh ./Antigravity-x64No sudo needed for updates.
./uninstall-antigravity.sh
./uninstall-antigravity-ide.shEach removes its app dir, launcher, icon, CLI symlink, and AppArmor
profile (the profile removal prompts for sudo). Your settings under
~/.antigravity-ide are left in place — delete by hand if you want.
If you previously installed to /opt/antigravity (e.g. by following the
older "just move it to /opt" advice), use
uninstall-system-wide-legacy.sh to clean that up before running the
user-local installer.
- The Antigravity Hub's auto-updater (
electron-updaterwith a generic provider) can detect new versions but on Linux it cannot replace an extracted-tarball install in place. Treat any update notice as a cue to re-download the tarball and re-run the install script. - On distros without AppArmor (Fedora, Arch, etc.) the AppArmor block is skipped entirely and Chromium's sandbox works out of the box.
- The IDE is a VS Code fork; settings live under
~/.antigravity-ide/. - The Nautilus "Open in Antigravity IDE" extension targets the Nautilus Python binding versions 4.1 / 4.0 / 3.0 (auto-detected). It only applies to GNOME / Nautilus — Nemo / Caja / Dolphin / Thunar would each need their own equivalent.

Do you see the "Open in IDE" button if you use this install?