Antigravity CLI: setup & compatibility

Official Google installation. This does not connect TokenRex.

1. 1

   Open Terminal on your Mac or Linux computer. Review Google's installer at the linked repository before running it.

2. 2

   Run the installation command below, then open a new terminal if the agy command is not yet available.

3. 3

   Run agy and follow the CLI's Google sign-in instructions. Start with a small read-only task in a folder you are authorized to access.

4. 4

   Use /config for interactive settings and /help for available commands. Review permissions before letting the agent edit files or execute commands.

curl -fsSL https://antigravity.google/cli/install.sh | bash
agy

1. 1

   Open PowerShell and review Google's installer before executing it.

2. 2

   Run the official command below, reopen PowerShell if necessary, then start agy and complete Google sign-in.

irm https://antigravity.google/cli/install.ps1 | iex
agy

Documented in release 1.1.13. This requires Gemini-native API compatibility; an OpenAI Chat Completions URL is not interchangeable.

1. 1

   Update to a CLI release supporting Gemini API-key mode. Open its settings.json and merge modelProvider: gemini with existing settings; do not replace permission settings.

2. 2

   Supply GEMINI_API_KEY privately in the environment used to launch agy. Use a credential accepted by your Gemini-compatible provider, not a TokenRex key.

3. 3

   Set GOOGLE_GEMINI_BASE_URL only to a provider-documented Gemini-native endpoint. Google documents the override but does not establish a TokenRex URL or arbitrary OpenAI model-ID support.

4. 4

   Start agy. Check that the banner or /help identifies Gemini API key credentials. Verify a short request with that provider before enabling agent actions.

{
  "modelProvider": "gemini"
}

Not directly verified. A custom base URL alone does not make two API formats compatible.

1. 1

   Do not set GOOGLE_GEMINI_BASE_URL to TokenRex's OpenAI-compatible base: the documented CLI mode uses Gemini-native requests.

2. 2

   Do not assume OPENAI_BASE_URL, OPENAI_API_KEY or arbitrary TokenRex model IDs work in agy. These are not established by the official CLI sources checked here.

3. 3

   For TokenRex today, choose a documented compatible tool such as OpenCode, Hermes Agent or Codex CLI from Integrations, and follow that tool's protocol-specific guide.

4. 4

   Recheck Google's CLI documentation when provider support changes. A protocol adapter would be a separate integration and must be tested before being recommended.