Skip to main content
Gemini CLI−3 Mixed

GILD Review

GILD's call and the buying facts behind it.

From GILD research

Should we adopt Gemini CLI?

When should each of your teams move from Gemini CLI to Antigravity CLI?

  1. 30-Second TakeKeep Gemini CLI only if you already hold a Code Assist subscription or bill Gemini through Google Cloud.
  2. Best fitHolders of a Gemini Code Assist Standard or Enterprise subscription, and teams billing Gemini through Vertex AI, that want an open-source terminal agent under central settings.GILD Review
  3. Consider another workflowTeams without a Code Assist subscription can no longer buy one. Start them on Antigravity CLI through Gemini Enterprise, or on Claude Code or Codex if Google Cloud does not hold your model spend.GILD Review

Drawn from 108 sources and 1 operator insight

GILD analysis

Gemini CLI Review

Keep Gemini CLI for teams that hold a Code Assist subscription or bill Gemini through Google Cloud, and give each team a move date before its last renewal. Google now sells its terminal agent as Antigravity CLI inside Gemini Enterprise. Until each team moves, one system settings file locks how Gemini CLI signs in and what it may run.

  • AI Coding Agents
  • Engineering Productivity

The decision

Best fit
Holders of a Gemini Code Assist Standard or Enterprise subscription, and teams billing Gemini through Vertex AI, that want an open-source terminal agent under central settings.
Consider another workflow
Teams without a Code Assist subscription can no longer buy one. Start them on Antigravity CLI through Gemini Enterprise, or on Claude Code or Codex if Google Cloud does not hold your model spend.
Adoption condition
Pin the sign-in method, force a sandbox, and allowlist MCP servers in the system settings file. Review every change before merge, and set each team's Antigravity CLI date before its final Code Assist renewal.

Basis: Google documentation and published pricing, its Antigravity CLI transition notice, and its Code Assist subscription sunset notice. Terminal-Bench 4.0, the leaderboard Stanford and the Laude Institute host, lists no Gemini CLI run as of October 25, so time accepted changes per engineer in your own pilot.

Buying & deployment factsWhat engineering leaders should verify before a broader rollout.
How you buy it

October 9, 2026

Google stopped new Code Assist sales. Subscribers can add licenses until January 31, 2027.

Source 1, Google, Gemini Code Assist Standard and Enterprise subscriptions: Gemini Code Assist Standard and Enterprise subscriptionsSource 3, Google, Quota and pricing: Quota and pricing

Details

Google stopped selling new Gemini Code Assist Standard and Enterprise subscriptions on October 9, 2026. Existing subscribers keep Gemini CLI until contract end, and can add licenses and renew annual plans until January 31, 2027 or monthly plans until December 31, 2027. Paid Gemini API keys and Vertex AI billing also run it.

Cost drivers

US$19

Per user per month on Standard with a one-year commitment. Enterprise is US$45.

Source 2, Google, Gemini Code Assist pricing: Gemini Code Assist pricingSource 3, Google, Quota and pricing: Quota and pricing

Details

For existing subscribers, Standard costs US$22.80 per user per month on a monthly commitment or US$19 on a one-year commitment, and Enterprise costs US$54 or US$45, billed monthly; Google lists these as hourly license fees. Gemini CLI allows 1,500 model requests per user per day on Standard and 2,000 on Enterprise. Past the cap, work moves to per-token billing through a Gemini API key or Vertex AI.

Where it runs

Node.js 20 terminal

On macOS, Windows, and Linux, in Cloud Shell, and in a GitHub Action.

Source 5, geminicli.com, Gemini CLI installation: Gemini CLI installationSource 6, Google, Gemini CLI headless mode: Gemini CLI headless modeSource 7, Google, run-gemini-cli GitHub Action: run-gemini-cli GitHub Action

Details

A Node.js 20 or later terminal app for macOS, Windows, and Ubuntu Linux, preinstalled in Cloud Shell and Cloud Workstations, plus headless runs in scripts and the run-gemini-cli GitHub Action.

What to verify

Sandbox off

Sandboxing is off unless configured, and Google does not vet gallery extensions.

Source 10, Google, Gemini CLI terms and privacy: Gemini CLI terms and privacySource 11, Google, Gemini API Additional Terms of Service: Gemini API Additional Terms of ServiceSource 8, Google, Gemini CLI sandboxing: Gemini CLI sandboxingSource 4, Google, Enterprise configuration: Enterprise configurationSource 9, geminicli.com, Gemini CLI extensions gallery: Gemini CLI extensions gallery

Details

Unpaid-tier and Google One sign-ins moved to Antigravity CLI on June 18, 2026; confirm engineers cannot fall back to an unpaid Gemini API key, whose content Google uses to improve its products. Sandboxing runs only when enabled by flag, environment variable, or settings, and the system settings file can enforce both the sign-in method and the sandbox. Google does not vet gallery extensions, so each one needs its own approval.

Sourced from Google documentation