On Linux, I have antigravity 2.0 installed (and, woof, do better guys, I shouldn’t have to chmod/chown things to root as part of getting an app set up, it’s 2026). What’s interesting though is I’m still stuck on 2.0.0. When I click “check for update”, nothing happens. It appears that the app is trying to use electron’s update flow, but that apparently only works if the app is packaged as an appimage? In the terminal, I see
08:42:07.482 › APPIMAGE env is not defined, current application is not an AppImage
each time I clikc that check for update button. Has anyone managed to get 2.0.6 or 2.0.10 installed on Linux? The binaries from the Antigravity 2.0 site are still 2.0.0.
Just untar the file and run it as user. No root needed. Using root for building a house is not the correct way to use Linux.
Pretty much what tuapuikia99 specified. I think the issue comes from that the old instructions wanted you to register certain package manager stuff (there were two repos supported IIRC). Currently is just a tar.gz. Un-compress it somewhere (e.g.: ~/.local/opt/Antigravity-x64/) and add it to your PATH at ~/.profile.
If you are on Arch there is a community managed package (this is what I currently use). There is also a community driven AppImage (haven’t tested it).
That does not work on Ubuntu. The program complains about chrome-sandbox not being owned by root and not having the correct access permissions.
How are you uncompressing the file? try with:
tar -xzpf Antigravity.tar.gz -C ~/.local/opt/
If it still doesn’t come with the permission enabled then is a bug:
chmod +x ~/.local/opt/Antigravity-x64/chrome-sandbox
Here is a link to Arch PKGBUILD: PKGBUILD - aur.git - AUR Package Repositories
There doesn’t seem to be explicit chmod calls there.
I was just double-clicking on the file in the file manager. I’ll try it with the xvpf flags. That being said, the issue with the permissions is secondary to the update function not working correctly.
Yeah, I’m pissed too. Updating via AUR isn’t the best too.
I’m not pissed, per se. I pointed antigravity at itself and told it to fix it and it did. (Basically just repackaging antigravity as an appimage then running it causes the update to come down the pipe. And then every time you do that you need to delete chrome-sandbox from the appimage because appimages don’t run as root or some such.) But I do think it would be nice if they fixed it. Somehow every other appimage in existence manages this with less trouble.