Gemini CLI Review: Who It Still Serves After Google's Move to Antigravity CLI

Confirm who can still sign in

Gemini CLI works for organization accounts with a Code Assist Standard or Enterprise license, for paid Gemini API keys, and for Vertex AI. Google's sunset page, updated October 26, 2026, says existing subscriptions keep working until the contract ends. Annual plans can auto-renew until January 31, 2027 and monthly plans until December 31, 2027, so plan for licensed sign-in to end at your final renewal. A customer asked Google to confirm this on GitHub on October 11, 2026, and Google had not answered by October 25. Teams without a license run Gemini CLI on a paid key or Vertex AI. Licensed users set GOOGLE_CLOUD_PROJECT. Google's pricing page states that content sent on the free Gemini API tier is used to improve its products, so enforce the sign-in method in system settings with security.auth.enforcedType.

Lock the settings that matter

Deploy a system override settings file, at /etc/gemini-cli/settings.json on Linux, which outranks user and workspace settings. Use it to force a Docker sandbox, allowlist MCP servers with mcp.allowed, restrict tools with the policy engine, and set security.disableYoloMode. Google's enterprise guide says these controls prevent accidental misuse and are not a boundary against a user with local administrator rights.

Plan for the daily request cap

Code Assist counts model requests, and one prompt in Gemini CLI or agent mode can make several. The cap of 1,500 requests per user per day on Standard or 2,000 on Enterprise is shared by both. A Google collaborator on the Gemini CLI repository wrote in January 2026 that these caps count all model calls, and that the limit on Pro models is lower and changes over time. One Code Assist Standard subscriber reported reaching the daily Pro limit after 20 to 30 minutes of use. Past the cap, Google's quota page routes work to a Gemini API key or Vertex AI at per-token rates, so decide in advance who may switch and on whose billing account.

Treat extensions like dependencies

Extensions package MCP servers, custom commands, hooks, subagents, and agent skills. Google's gallery lists 2,178 of them and says it does not vet their functionality or security, so keep an approved list and expose only the MCP tools a task needs with includeTools.

Put a date on the Antigravity decision

Antigravity CLI keeps Agent Skills, Hooks, Subagents, and Extensions (as Antigravity plugins), without one-to-one feature parity at launch, and Google Cloud projects can use it now. Google's migration guide converts extensions to plugins with agy plugin import gemini and reads GEMINI.md and AGENTS.md files unchanged. Workspace skills must move by hand from .gemini/skills to .agents/skills, and MCP servers move into mcp_config.json, where the url or httpUrl key becomes serverUrl. Google asks Code Assist customers to move to Gemini Enterprise, which includes Antigravity, before the plan's final renewal or contract end. Run both agents on the same tasks well before that date.