Documentation Index
Fetch the complete documentation index at: https://mintlify.com/google-antigravity/antigravity-cli/llms.txt
Use this file to discover all available pages before exploring further.
Antigravity CLI uses your system keyring to manage credentials. If no active session exists, it falls back to Google Sign-In automatically. The exact sign-in experience depends on whether you’re running the CLI locally or over an SSH connection.
Sign in
When you run Antigravity CLI on your local machine, it opens your default browser automatically to complete the Google Sign-In flow.Start the CLI
Launch Antigravity CLI in your terminal. If no active session is found in the system keyring, authentication starts automatically.
Complete sign-in in the browser
Your default browser opens to the Google Sign-In page. Sign in with your Google account.
Return to the terminal
After you authorize access, the browser confirms the sign-in and you can close the tab. The CLI resumes in your terminal.
When you run Antigravity CLI over an SSH session, the CLI detects the remote environment and cannot open a browser on your behalf. Instead, it prints an authorization URL for you to open locally.Start the CLI over SSH
Connect to your remote machine and launch Antigravity CLI. If no active session is found, the CLI prints an authorization URL to the terminal output.
Open the URL on your local machine
Copy the authorization URL from the terminal and open it in a browser on your local machine.
Complete sign-in in the browser
Sign in with your Google account on the Google Sign-In page.
Return to the remote terminal
After you authorize access, the CLI on your remote machine detects the completed sign-in and continues.
Sign out
To clear your saved credentials, run /logout inside the CLI. This removes the stored session from the system keyring.
Enterprise and GCP access
If your organization uses enterprise access, you connect a GCP project during the onboarding flow. See Enterprise authentication with GCP for details.