openclaw - 💡(How to fix) Fix [Feature]: Add Antigravity CLI (agy) as CLI backend to replace deprecated google-gemini-cli

Summary

Google announced on May 19, 2026 (Google I/O) that Gemini CLI is being transitioned to Antigravity CLI (agy). Individual-tier users (Google AI Pro, Ultra, free Gemini Code Assist) have until June 18, 2026 before Gemini CLI stops serving requests.

OpenClaw currently uses google-gemini-cli as a CLI backend for Gemini model access. This backend will stop working on June 18, 2026 for non-enterprise users.

Request

Add antigravity-cli (binary: agy) as a new CLI backend provider, similar to how google-gemini-cli and opencode (Claude Code) are supported today.

Key differences from Gemini CLI

Context

• Official announcement: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/
• Migration docs: https://antigravity.google/docs/gcli-migration
• GitHub repo: https://github.com/google-antigravity/antigravity-cli
• Deadline: June 18, 2026 (individual tier only; enterprise unaffected)

Workaround

Users can use GEMINI_API_KEY with the google provider (direct API, no CLI needed) which is unaffected by this transition. However, this loses the agentic capabilities (tools, skills, subagents) that the CLI backend provides.

Notes

• The previous google-antigravity-auth plugin was removed in v2026.2.22 due to Google banning accounts. The new Antigravity CLI is the official replacement path from Google and should not carry the same ban risk as the old OAuth-routing approach.
• Enterprise users with Gemini Code Assist Standard/Enterprise licenses are unaffected and can continue using google-gemini-cli indefinitely.

Problem to solve

OpenClaw users who rely on the google-gemini-cli CLI backend for agentic Gemini access (tools, skills, subagents, shell execution) will lose functionality on June 18, 2026 when Google deprecates Gemini CLI for individual-tier accounts.

The current google provider with GEMINI_API_KEY only provides text-in/text-out API access — it cannot run tools, execute shell commands, or leverage Gemini's agentic capabilities that the CLI backend enables.

Without an antigravity-cli (agy) backend, these users must either:

• Downgrade to API-only mode (losing agentic features)
• Pay for enterprise licensing to keep using Gemini CLI
• Leave OpenClaw for a framework that supports the new CLI

This affects anyone using google-gemini-cli as their primary or fallback model with a personal Google account — a significant portion of the user base given Gemini CLI's popularity as a free, full-featured backend.

Proposed solution

Desired behavior/API/UX with as much specificity as possible.

Add antigravity-cli as a registered CLI backend in the Google provider plugin (extensions/google/cli-backend.js), alongside the existing google-gemini-cli backend.

Expected behavior:

1. New backend registration: Register antigravity-cli (binary: agy) as a CLI backend with appropriate args, output parsing, and session management — mirroring how google-gemini-cli is registered today.

2. Model ref routing: google/* model refs should route through antigravity-cli when the agy binary is detected on PATH and gemini is absent (or after June 18 when gemini stops responding).

3. Auth integration: Support Antigravity CLI's OAuth flow via openclaw models auth login --provider antigravity-cli, storing tokens in auth-profiles.json under an antigravity-cli:<email> profile.

4. Migration path: When google-gemini-cli backend fails with an auth/connection error and agy is available on PATH, suggest or auto-fallback to antigravity-cli.

5. Config example:

   {
     "agents": {
       "defaults": {
         "model": { "primary": "google/gemini-3.1-pro-preview" },
         "cliBackends": {
           "antigravity-cli": { "command": "agy" },
           "google": { "command": "agy" }
         }
       }
     }
   }

6. Normalization: Handle the same google-gemini-cli → google model ref normalization for antigravity-cli, so isCliProvider("google") matches the new backend key.

7. Backward compatibility: Keep google-gemini-cli backend functional for enterprise users who retain Gemini CLI access indefinitely. Detect which binary is available and route accordingly.

Alternatives considered

No response

Impact

Affected users/systems/channels:

• All OpenClaw users running google-gemini-cli as primary or fallback model with personal Google accounts (Google AI Pro, Ultra, or free Gemini Code Assist)
• Cron jobs, subagents, and automated workflows that depend on Gemini CLI's agentic capabilities (tool use, shell execution, file editing)
• Telegram, Slack, and other channel users whose conversations route through the Gemini CLI backend

Severity: Blocks workflow — after June 18, 2026, the google-gemini-cli backend will return auth errors on every request. All conversations and cron jobs using Gemini as primary will fail and cascade to fallback models (if configured) or return no response at all.

Frequency: Always — this is a hard deprecation, not an intermittent failure. Every request to google-gemini-cli will fail after the deadline.

Consequence:

• Users without fallback models configured will have a completely non-functional bot
• Users with fallbacks (e.g., Claude Code) will silently shift all traffic to paid providers, increasing costs unexpectedly
• Agentic features (tool use, shell commands, subagents) are lost entirely when falling back to the google API-only provider
• Cron jobs and automated pipelines will fail or produce degraded output
• ~30 days to implement before the deadline hits

Evidence/examples

No response

Additional information

No response