Skip to main content

Buyer guide

Gemini CLI or Antigravity CLI: Planning the Decision

Code Assist sign-in to Gemini CLI ends with each contract, while paid API keys keep working. Set every team a move date to Antigravity CLI ahead of its last renewal.

Reading time
4 min read
Sources
18 cited
In this piece
2 products

Move each team to Antigravity CLI before its final Code Assist renewal. Gemini CLI keeps working only while a Code Assist contract or a paid API key covers it. Google stopped selling new Code Assist subscriptions on October 9, 2026 and supports existing ones until each contract ends. Subscribers can add licenses and renew annual plans until January 31, 2027, and renew monthly plans until December 31, 2027. Google asks them to move to Gemini Enterprise, which includes Antigravity, before the final renewal.

When you need this

  • Engineers who used Gemini CLI on personal Google AI Pro or Ultra plans lost access on June 18, 2026.
  • Your Code Assist subscription is nearing its last renewal.
  • A team without a Code Assist subscription wants Gemini CLI, and a new subscription is no longer for sale.
  • Teams rely on Gemini CLI extensions, custom commands, or MCP servers and need to know what carries over.
  • You run Gemini CLI in CI and need those pipelines on a supported sign-in.

Evaluation criteria

  1. Sort engineers by account type

    Who can still sign in to Gemini CLI?

    Look forCode Assist Standard and Enterprise organizations keep Gemini CLI until each contract ends. Google's troubleshooting page limits Code Assist features to users with an active Standard or Enterprise license, so plan for Code Assist sign-in to Gemini CLI to stop on the contract's end date. Paid Gemini and Gemini Enterprise Agent Platform API keys keep working, and Google has announced no end date for them. Personal Google AI Pro and Ultra plans and the free individual tier moved to Antigravity CLI. Teams without a subscription cannot buy one after October 9, 2026, so they run Gemini CLI on a paid API key or Vertex AI, or start on Antigravity.

  2. Inventory what each team depends on

    Which extensions, skills, hooks, and MCP servers would a move touch?

    Look forList them per team. Google says Antigravity CLI keeps Agent Skills, Hooks, Subagents, and Extensions, which become Antigravity plugins, without one-to-one feature parity at launch.

  3. Test the migration path

    How much rework does a move take?

    Look forRun agy plugin import gemini, which converts extensions into plugins and their commands into skills. GEMINI.md files work unchanged. Move workspace skills from .gemini/skills/ to .agents/skills/ by hand, move MCP servers into mcp_config.json files, and rename url or httpUrl to serverUrl for remote servers.

  4. Confirm the billing route

    Which plan pays for each tool?

    Look forPay for Gemini CLI from your Code Assist subscription until its contract ends, and confirm how Antigravity CLI bills before anyone tests it. Antigravity's enterprise docs list a Gemini Enterprise Standard or Plus seat, or a Cloud project billed by consumption through the Pay-as-you-go edition or the API. They do not list Code Assist licenses. Since August 20, 2026, Gemini Enterprise Standard and Plus seats include Antigravity, with US$10 or US$15 of credit per user per month pooled weekly across licensed users. Since September 17, 2026, Gemini Enterprise Standard or Plus subscriptions bought or renewed online no longer include Code Assist features. A Code Assist Standard user reported in June 2026 that Antigravity CLI accepted the sign-in and then failed each prompt with a Vertex AI permission error. In the transition thread, users report that Antigravity CLI does not accept the Code Assist plan and bills Cloud projects by consumption instead, and one reports a bug that routed calls to Vertex AI regardless of entitlement.

  5. Run both on the same tasks

    Which agent produces more accepted, reviewed changes for your work?

    Look forRun a two-week pilot on real tickets that counts changes merged after review and the review time each needed. Record the model each agent actually ran. Enterprise customers report that Antigravity received new Gemini Flash models on release day while Gemini CLI waited weeks. Google's Code Assist docs now state that "Gemini CLI is not optimized for the latest Gemini models."

Questions to ask vendors

  1. Which engineers used Gemini CLI on personal plans before June 18, 2026, and what do they use now?
  2. Which CI jobs call Gemini CLI, and which sign-in does each use?
  3. When does each Code Assist contract reach its final renewal or end date?
  4. Which engineers move to a paid API key, and which to Antigravity CLI, on the day each Code Assist contract ends? Ask your Google account team to confirm that date in writing.
  5. Which Antigravity CLI features does your workflow need that it lacks today?
  6. Which Gemini Enterprise edition, or Gemini Enterprise Agent Platform billing, will carry Antigravity CLI for each team?

Red flags

  • Engineers still trying to sign in to Gemini CLI with Google AI Pro or Ultra accounts.
  • A budget line for new Code Assist subscriptions, which Google stopped selling on October 9, 2026.
  • Testing Antigravity CLI against a production Cloud project before anyone confirms how it bills.
  • Treating a plugin import as a finished migration without moving workspace skills and MCP settings.
  • Reaching the final Code Assist renewal without running both agents on your own tasks.

Products in this piece

Sources

Official documentation
14
Public source
4
  1. Gemini Code Assist docs: Gemini Code Assist Standard and Enterprise subscriptionsOfficial documentationdocs.cloud.google.com
  2. Gemini Code Assist docs: DeprecationsOfficial documentationdevelopers.google.com
  3. Gemini Code Assist release notesOfficial documentationdocs.cloud.google.com
  4. Gemini Enterprise release notesOfficial documentationdocs.cloud.google.com
  5. Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI (May 19, 2026)Official documentationdevelopers.googleblog.com
  6. Antigravity CLI docs: Migrating from Gemini CLIOfficial documentationantigravity.google
  7. Antigravity docs: Antigravity in Gemini EnterpriseOfficial documentationantigravity.google
  8. Gemini Enterprise docs: Quotas and pay-as-you-go usageOfficial documentationdocs.cloud.google.com
  9. Gemini CLI docs: Quota and pricingOfficial documentationgeminicli.com
  10. Gemini Code Assist docs: Gemini CLIOfficial documentationdocs.cloud.google.com
  11. Gemini CLI docs: ExtensionsOfficial documentationgeminicli.com
  12. Gemini CLI docs: Agent SkillsOfficial documentationgeminicli.com
  13. Gemini CLI docs: HooksOfficial documentationgeminicli.com
  14. GitHub issue 28625: Enterprise Gemini CLI users waiting for Gemini 3.5 and 3.6 Flash (Aug 2, 2026)Public sourcegithub.com
  15. GitHub discussion 27274: user comments on the Antigravity CLI transition (May to Jul 2026)Public sourcegithub.com
  16. Gemini Code Assist docs: Troubleshoot access to Gemini Code Assist featuresOfficial documentationdocs.cloud.google.com
  17. GitHub issue 437 on antigravity-cli: Gemini Code Assist Standard account cannot use Antigravity CLI without Vertex AI pay-as-you-go permissions (Jun 19, 2026)Public sourcegithub.com
  18. GitHub issue 29712: Impact of the Gemini Code Assist Standard/Enterprise subscription sunset on Gemini CLI authentication (Oct 11, 2026)Public sourcegithub.com

Keep reading

  1. ComparisonGoogle Antigravity vs Gemini CLI: Which Google Agent After the Code Assist Sunset?Antigravity is Google's path forward, so time each team's switch before its final Code Assist renewal. Who can still use each, how each is billed, and what carries over.
  2. Buyer guideGoogle Antigravity Workflow PlaybookSix Antigravity setup and review habits for teams whose engineers get different results from the same agent, or whose quota runs out mid-task.
  3. Buyer guideAntigravity in Gemini Enterprise: Rollout and Controls ChecklistEditions, roles, APIs, sign-in, the admin defaults to change before day one, model approval, logging, and spend caps for a team rollout.
Read the research