Antigravity 2.x on Fedora Linux (no official RPM)

Antigravity 2.x on Fedora Linux (without official RPM)

Practical guide to install, organize, and update Google Antigravity 2.x, Antigravity IDE, and CLI (agy) on Fedora Linux until official RPM packages are made available.


Current Scenario

Currently, Google does not yet provide:

  • Updated official RPM for Fedora

  • Full integration with dnf

  • Native automatic updates

Because of this, many users end up:

  • Running the app directly from the Downloads folder

  • Breaking launchers

  • Losing paths

  • Having issues with updates

  • Creating inconsistent symlinks

This guide standardizes the installation using:

  • /opt

  • /usr/local/bin

  • Update scripts

  • Conventional Linux structure


Recommended Structure

Antigravity 2.x

/opt/antigravity

Antigravity IDE

/opt/antigravity-ide

Global Symlinks

/usr/local/bin/antigravity
/usr/local/bin/antigravity-ide


1. Download the applications

Manually download:

  • Antigravity 2.x

  • Antigravity IDE

from Google’s official links.

Extract the .tar.gz files.


2. Move to /opt

Antigravity 2.x

sudo mv ~/Antigravity /opt/antigravity


Antigravity IDE

sudo mv ~/Antigravity\ IDE /opt/antigravity-ide


3. Create global symlinks

Antigravity 2.x

sudo ln -sf \
/opt/antigravity/Antigravity-x64/antigravity \
/usr/local/bin/antigravity


Antigravity IDE

sudo ln -sf \
/opt/antigravity-ide/antigravity-ide/antigravity-ide \
/usr/local/bin/antigravity-ide


4. Permissions

sudo chmod +x /opt/antigravity/Antigravity-x64/antigravity

sudo chmod +x \
/opt/antigravity-ide/antigravity-ide/antigravity-ide


5. Verify installation

which antigravity
which antigravity-ide

Expected:

/usr/local/bin/antigravity
/usr/local/bin/antigravity-ide


6. Test execution

Antigravity

antigravity --no-sandbox


IDE

antigravity-ide --no-sandbox


Common Issue: Electron Sandbox

On Fedora (especially Wayland + SELinux), Electron frequently fails with the sandbox.

Solution:

--no-sandbox

You may need to add this to your desktop launchers.


7. Create Antigravity 2.x updater

Create:

sudo nano /usr/local/bin/update-antigravity

Paste the script from the LinuxCapable article.

IMPORTANT:

The file must start directly with:

#!/usr/bin/env bash

DO NOT paste:

sudo tee ... <<EOF

This is a terminal command, not the script’s content.


Permission

sudo chmod +x /usr/local/bin/update-antigravity


Fix CRLF (optional)

sudo sed -i 's/\r$//' /usr/local/bin/update-antigravity


Update Antigravity

sudo update-antigravity


8. Create Antigravity IDE updater

Create:

sudo nano /usr/local/bin/update-antigravity-ide

Paste the corresponding script from LinuxCapable.


Permission

sudo chmod +x /usr/local/bin/update-antigravity-ide


Update IDE

sudo update-antigravity-ide


9. Verify final symlinks

readlink -f /usr/local/bin/antigravity

readlink -f /usr/local/bin/antigravity-ide

Expected:

/opt/antigravity/Antigravity-x64/antigravity

/opt/antigravity-ide/antigravity-ide/antigravity-ide


10. Future updates

Antigravity 2.x

sudo update-antigravity


Antigravity IDE

sudo update-antigravity-ide


CLI (agy)

Normally, the CLI installs to:

~/.local/bin/agy

Verify:

which agy
agy --version

The folder:

~/.gemini

is only CLI configuration/cache and should not be moved.


Common Issues

“command not found”

Verify:

ls -l /usr/local/bin


Empty file

Many users paste:

sudo tee ... <<EOF

INSIDE nano.

This breaks the script.

The file should start only with:

#!/usr/bin/env bash


Broken Symlink

Verify:

readlink -f /usr/local/bin/antigravity


Folder with spaces

Avoid:

Antigravity IDE

Prefer:

antigravity-ide

to avoid future issues in:

  • Scripts

  • Shell

  • Automations

  • Systemd

  • Launchers


Recommended Final Structure

/opt/antigravity
/opt/antigravity/Antigravity-x64

/opt/antigravity-ide
/opt/antigravity-ide/antigravity-ide

/usr/local/bin/antigravity
/usr/local/bin/antigravity-ide


Conclusion

Until Google provides updated official RPMs for Fedora:

  • This method is the most stable

  • It keeps the system organized

  • It facilitates updates

  • It avoids path issues

  • It preserves future compatibility

  • It follows conventional Linux standards

It also makes future migration to the official RPM easier when it becomes available.

is this an final stucture ? i am okay to wait for the update but i heard that the google ditched the repository and suggesting this tarbol installation ? is it really the case ?

Yup, use the tarball :+1:

Hello! I was having the same issues and thought an easy way to package antigravity would be interesting so quickly built this: