Google Antigravity is a Google development environment with both a GUI product and a terminal-first CLI. On Ubuntu 26.04, the sane path is to use the vendor installer script for Linux, not to guess at an APT package name that may or may not exist on your host. If your goal is to install Google Antigravity Ubuntu 26.04 on a workstation, cloud VM, or remote SSH box, this procedure keeps the moving parts explicit and gives you a clean verification path. The steps below use the installation method documented for macOS and Linux, and they call out the places where Google may change paths, package names, or onboarding screens later.
Ubuntu 26.04 compatibility matters for two reasons. First, Ubuntu 26.04 LTS ships with current userland changes that can expose weak third-party installers. Second, many admins will reach this release by upgrade rather than fresh install, which means old shell profiles, stale keyrings, and existing browser sessions can affect the first-run flow. Google’s published material shows a Linux install route and browser-based authentication, while the Antigravity CLI README states that remote SSH sessions fall back to a printed authorization URL.
Prerequisites
- Ubuntu 26.04 LTS, either a fresh installation or an upgraded host; upgraded systems deserve extra attention for inherited shell config and PATH collisions.
- sudo access or root privileges, because package cache updates and dependency installation write to system locations.
- A working internet connection, because the installer is fetched over HTTPS and authentication uses a browser or an authorization URL.
- curl, bash, ca-certificates, and a functional system keyring or browser session; the official Linux install command pipes a fetched shell script to bash.
- Practical hardware baseline: for a desktop session, 6 GB RAM is a reasonable floor on Ubuntu 26.04 according to third-party release coverage; a headless CLI-only host can run with less, but that depends on the rest of the workload.
Step-by-Step Installation
1. Update package indexes and install base dependencies
Run:
sudo apt update
sudo apt install -y curl ca-certificates bash
This step ensures the host can fetch the installer over HTTPS and execute it with the expected shell tools.
Expected terminal output:
Hit:1 http://archive.ubuntu.com/ubuntu resolute InRelease
Hit:2 http://security.ubuntu.com/ubuntu resolute-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
curl is already the newest version (...)
ca-certificates is already the newest version (...)
bash is already the newest version (...)
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded
What can go wrong: if apt update fails with TLS or mirror errors, fix basic network or repository problems first; do not debug the Antigravity installer on top of a broken package manager.
2. Confirm release state on upgraded hosts
Run:
lsb_release -a
uname -r
This step confirms that the box is actually on Ubuntu 26.04 and helps catch mixed-release upgrade states before you blame the application.
Expected terminal output:
Distributor ID: Ubuntu
Description: Ubuntu 26.04 LTS
Release: 26.04
Codename: [PLACEHOLDER: vendor codename may differ across preview and GA documentation]
7.0.0-xx-generic
What can go wrong: on systems upgraded in place, third-party repositories pinned for an older release can leave you with partial upgrades, broken libc dependencies, or a stale browser package. Remove or disable those repos before continuing.
3. Inspect the official installation method before executing it
Run:
curl -fsSL https://antigravity.google/cli/install.sh | sed -n '1,120p'
This step lets you inspect the installer rather than pasting a blind pipe into a privileged shell. The official README publishes the Linux install method as a curl | bash command, so checking the script first is the professional move.
Expected terminal output:
#!/usr/bin/env bash
set -euo pipefail
...
What can go wrong: if the request returns HTML, a login page, or a CDN error instead of shell content, stop there and verify the download URL from the official docs page.
4. Run the official Linux installer
Run:
curl -fsSL https://antigravity.google/cli/install.sh | bash
This is the vendor-documented installation path for Antigravity CLI on Linux. Google’s current README lists this exact command for macOS and Linux.
Expected terminal output:
Downloading Antigravity CLI...
Verifying archive...
Installing to /home/$USER/.local/bin/[PLACEHOLDER: antigravity executable name]
Updating shell profile...
Installation complete.
Open a new shell or reload your profile to continue.
What can go wrong: if the installer cannot write into your user profile, it may finish without putting the binary on PATH; verify the install location before moving on. The exact binary name is not exposed in the retrieved source, so treat it as a discoverable value rather than a guessed command.
5. Reload the shell environment
Run:
exec "$SHELL" -l
This step reloads the login shell so any PATH changes added by the installer take effect immediately.
Expected terminal output:
[no output on success]
What can go wrong: if your shell is not reading the profile file that the installer modified, the binary still will not resolve. Check ~/.profile, ~/.bashrc, ~/.zprofile, or the shell-specific startup file the installer touched.
6. Discover the installed command name and path
Run:
find ~/.local/bin /usr/local/bin -maxdepth 1 -type f | grep -Ei 'antigravity'
This step avoids making up a binary name when the available source confirms the product and installer but does not expose the final executable name. It also tells you whether the installer wrote into a user-local or system-local prefix.
Expected terminal output:
/home/youruser/.local/bin/[PLACEHOLDER: antigravity or ag CLI binary name]
What can go wrong: no output usually means the installer failed silently, wrote somewhere outside the standard prefixes, or your home directory was not writable during install. Re-run the installer with shell tracing only after you capture the current environment.
7. Verify the binary responds
Run:
[PLACEHOLDER: /home/youruser/.local/bin/antigravity] --help
This verifies that the installed binary is executable and that the runtime linker can start it. Use the exact path from the previous step if PATH is still not correct.
Expected terminal output:
Usage: [PLACEHOLDER: antigravity] [command] [options]
...
What can go wrong: Permission denied points to a bad mode bit or a noexec mount on the install path; No such file or directory can also mean the ELF interpreter or a required shared object is missing.
8. Authenticate the CLI
Run:
[PLACEHOLDER: antigravity binary] # first interactive launch
The first run is needed because the CLI authenticates through the system keyring and falls back to Google Sign-In when no active session exists. On a remote SSH session, the CLI is documented to print an authorization URL instead of trying to open a browser on the remote host.
Expected terminal output:
No active session found.
Opening browser for Google Sign-In...
Remote SSH example:
SSH session detected.
Open the following URL locally to authorize this device:
https://[PLACEHOLDER: antigravity auth URL]
What can go wrong: keyring integration can fail on stripped-down desktops, minimal cloud images, or custom window manager setups. In that case, use the fallback browser flow or the SSH URL path.
9. Optional: create a stable wrapper on multi-user systems
Run:
sudo install -d -m 0755 /usr/local/bin
sudo ln -sf /home/$USER/.local/bin/[PLACEHOLDER: antigravity binary] /usr/local/bin/antigravity
This gives you a predictable command path for operational docs, shell scripts, and remote sessions where user-local PATH handling is inconsistent. Do this only after you confirm the real installed binary name.
Expected terminal output:
[no output on success]
What can go wrong: if multiple admins share the box, a symlink to one user’s home directory is fragile. In that case, install per user or use the vendor’s system-wide method if Google publishes one later.
Verification
After installation and authentication, verify the command path, help text, and session behavior.
Run:
command -v antigravity || find ~/.local/bin /usr/local/bin -maxdepth 1 -type f | grep -Ei 'antigravity'
[PLACEHOLDER: antigravity binary] --help
The first command confirms shell resolution; the second confirms the executable launches correctly and exposes its command surface.
Expected output example:
/usr/local/bin/antigravity
Usage: antigravity [command] [options]
Commands:
auth
chat
session
logout
The exact subcommands may differ by build, but you should see standard usage output rather than a shell error, a segfault, or a missing-library message. The README also documents /logout as the sign-out action, which is a useful sanity check that you are dealing with the expected CLI.
Basic Configuration
Shell alias for remote work
If you use the CLI mostly over SSH, define a short alias or wrapper and pin environment variables in your shell profile.
Run:
printf '\nalias ag="[PLACEHOLDER: antigravity binary]"\n' >> ~/.bashrc
source ~/.bashrc
This reduces path noise in remote sessions and avoids hard-coding a user-local binary path into every command you type.
Session hygiene
Google’s README states that settings and permissions sync and that the CLI stores credentials via the system keyring when possible. On shared admin workstations, keep it tied to the least-privileged user account that actually uses the tool, and use /logout before handing the session to someone else.
[Related: How to manage APT repositories on Ubuntu]
[Source: official docs URL]
Troubleshooting
curl: (6) Could not resolve host: antigravity.google
Cause: DNS resolution is broken, the host has no outbound connectivity, or a proxy is intercepting requests badly. Fix: verify /etc/resolv.conf, test curl https://www.google.com, and export the correct http_proxy or https_proxy variables if the environment requires them.
bash: line 1: syntax error near unexpected token '<'
Cause: the installer URL returned HTML instead of a shell script, usually because of a bad redirect, captive portal, SSO gateway, or copied marketing URL. Fix: inspect the fetched content with curl -fsSL ... | sed -n '1,40p' and pull the installer URL again from the official docs or product page.
antigravity: command not found
Cause: the installer completed, but the shell profile did not reload, the installer wrote outside the current PATH, or it modified a startup file your shell does not read. Fix: locate the binary with find ~/.local/bin /usr/local/bin -maxdepth 1 -type f | grep -Ei 'antigravity', then add that directory to PATH or call the binary by full path.
Permission denied
Cause: the installed file is not executable, the target filesystem is mounted with noexec, or the symlink points into a directory with restrictive permissions. Fix: verify mode bits with ls -l, correct them with chmod 0755 [PLACEHOLDER: binary] if needed, and move the binary to an executable filesystem if the mount policy forbids execution.
No active session found followed by repeated browser auth failures
Cause: the keyring backend is unavailable, the default browser on the host is broken, or the remote session is trying to launch a local GUI flow. Fix: use the SSH authorization URL path documented by the CLI, complete sign-in from a local browser, and check whether the desktop keyring service is running on GUI hosts.
