Skip to content
NorviTech Helios
Browse the Helios guide

Helios / User guide / Gemini through Antigravity

Gemini through Antigravity

Set up Google Antigravity account sign-in for Gemini sessions in Helios, verify live models and understand headless permissions.

Helios 0.114.4 · Source reference ↗

Install Google Antigravity

Helios’s Gemini integration uses Google’s Antigravity CLI, named agy. Follow the official CLI setup, then check and open it:

agy --version
agy

Complete Google-account sign-in in the interactive CLI. This is a separate integration from the generic Gemini CLI and does not fall back to a Gemini API-key route.

Check the account and live models

In Antigravity, use /usage to inspect current account quota. In a terminal, list models with:

agy models

Refresh Settings → Providers → Google · Gemini in Helios. A discovered model catalogue and verified sign-in are separate signals. Helios uses the live model names and capabilities reported by the CLI.

Discovery checks PATH, ~/.local/bin and HELIOS_GOOGLE_BINARY. If desktop discovery fails, check the app’s launch environment.

Keep the intended account route

This Helios route uses the Google account allowance. It rejects API/custom-provider routing and automatic AI-credit overages. Antigravity’s native settings must match that route; Helios does not rewrite them for you.

Check Antigravity’s provider selection and credit-fallback setting if Helios refuses startup. The repository’s Google integration reference documents the exact configuration checks.

Start in a project folder

  1. Choose a real project or a separate Git worktree.
  2. Select a discovered Google/Gemini model.
  3. Choose a supported reasoning level and execution mode.
  4. Ask for a read-only explanation of one or two named files.
  5. Compare the answer with the actual code before moving to edits.

Google sessions require a project folder and cannot start at your home-directory root. The first message waits for native initialization. A second submission during startup remains a draft; send it after the chat is ready.

Understand the integration limits

Execution offers Sandboxed, Accept edits, Bypass and Read only. Sandboxed operation can still allow workspace writes. The headless path cannot show or answer interactive approval requests.

Antigravity uses its own browser integration. Composer image references remain text paths in the current Helios route. Read permission differences before assuming parity with another provider.