Gemini CLI Is Dead — Don't Migrate to Antigravity Blind

Google announced at I/O on May 19 that Gemini CLI — 104k GitHub stars, Apache 2.0 licensed, built in TypeScript by an active open-source community — stops serving requests for all free, Pro, and Ultra individual users on June 18, 2026. That is 30 days from announcement, 27 days from today. The replacement, Antigravity CLI, is closed-source, written in Go, and does not have feature parity at launch. If your workflows depend on gemini-cli, this is not a heads-up. It is a countdown.

TL;DR

• Deadline: June 18, 2026 — Gemini CLI stops serving requests for free, Pro, and Ultra individual accounts. No grace period.
• Replacement: Antigravity CLI — closed-source, Go-based, async architecture. No 1
  feature parity at launch.
• Enterprise exemption: Gemini Code Assist Standard/Enterprise licenses are unaffected.
• Action now: Audit every script, CI job, and pipeline that touches Gemini CLI endpoints. Parallel-install Antigravity CLI and validate before the cutoff.

Gemini CLI Shutdown — What Happened

Google’s official blog post is blunt: Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests on June 18, 2026 for anyone on Google AI Free, Pro, or Ultra individual accounts. Gemini Code Assist for GitHub will block new installations on the same date and stop serving existing installations in the weeks following. The 30-day window between the May 19 announcement and the June 18 cutoff is the entire migration runway.

Enterprise customers on Gemini Code Assist Standard or Enterprise licenses keep access. So do developers using paid Gemini API keys or the Google Cloud-backed Gemini Enterprise Agent Platform. Everyone else moves to Antigravity CLI or loses terminal-based access entirely.

Antigravity CLI is the designated successor. It shares the same agent harness as Antigravity 2.0, Google’s new desktop application announced at I/O. Agent Skills, Hooks, Subagents, and Extensions are supposed to carry over — Extensions become “Antigravity plugins.” But Google’s own announcement admits there will not be 1

feature parity at launch. And here is the detail that should concern anyone planning a migration: according to independent analysis from jangwook.net, as of May 21 the Antigravity CLI executable (agy) does not exist on any public package manager. The migration path Google is asking you to commit to is not fully available to test.

As of May 21, 2026, the agy executable is not published on any public package manager. If you are planning CI/CD migration, verify availability before scripting installs.

Why This Matters

The technical migration is not trivial. Antigravity CLI replaces Gemini CLI’s synchronous session model with asynchronous background workflows. It orchestrates multiple agents for complex tasks in the background, which means your terminal session is no longer locked during execution. That sounds like an upgrade on paper, but it is a fundamentally different execution model. Any script that expects synchronous request-response behavior from gemini-cli will not work the same way against agy. This is not apt upgrade. It is a parallel-install-and-validate workflow, and the validation window is shrinking daily.

The CI/CD exposure is the most underestimated risk. Interactive terminal users will notice the change and adapt. But headless invocations — cron jobs, GitHub Actions workflows, GitLab CI steps, pre-commit hooks — those will silently break on June 18 when the API stops responding. If you have not audited every non-interactive usage of Gemini CLI in your org, start today. Grep your repos for gemini-cli, gemini API endpoint calls, and any wrapper scripts that abstract the tool name.

Then there is the quota problem. Multiple developers have already reported hitting their weekly Antigravity CLI quota with just a handful of requests. The issues tracker is filling with complaints about usage limits that are materially stricter than what Gemini CLI offered. Google has not published a transparent quota comparison between old and new tiers. If your workflows are high-volume, you may discover on migration day that your usage pattern exceeds what your current subscription allows — and there is no fallback to gemini-cli after June 18.

The comparison point developers should be thinking about is Claude Code and Aider. Both are terminal-first coding tools. Claude Code is subscription-based ($20–$200/month) and closed-source but has never pulled a bait-and-switch on its access model. Aider is fully open-source, model-agnostic, and free — you pay only for API tokens. Neither tool has a history of sunsetting access with 30 days’ notice. If the Antigravity CLI quota restrictions prove as severe as early reports suggest, evaluating alternatives before migrating is not paranoia. It is risk management.

Before migrating, run grep -r "gemini-cli\|gemini" .github/workflows/ scripts/ .gitlab-ci.yml Makefile across your repositories. Catch every headless invocation now, not on June 18.

The Take

This is the Google playbook, and I want to be precise about why it is worse than the usual product shutdown.

Google took an Apache 2.0 open-source project with 104k stars and an active contributor community, let developers invest time building skills, extensions, and integrations around it, and then announced a 30-day forced migration to a closed-source replacement. Antigravity CLI’s GitHub page shows a changelog, a README, and a GIF. No source code. Developers who contributed to the Gemini CLI repository are publicly asking whether their work funded a proprietary product. They deserve a straight answer, and they have not gotten one.

The 30-day window is not a courtesy. It is designed to create urgency that prevents evaluation. Thirty days is enough time to swap a binary but not enough time to validate a fundamentally different execution model across a real codebase. Google knows this. The window exists to move users onto the new platform before they have time to ask whether the new platform deserves their commitment.

My recommendation is concrete: do not migrate blind. Spend the first week auditing your Gemini CLI surface area — every script, every CI step, every integration. Spend the second week testing Antigravity CLI in a sandboxed environment against your actual workflows, not Google’s demo scenarios. If the quota limits or feature gaps are blockers, you still have two weeks to evaluate Claude Code or Aider as replacements. The worst outcome is migrating to Antigravity CLI on June 17, discovering a breaking incompatibility on June 19, and having no fallback.

Google has earned the skepticism. The pattern of free-tier access followed by forced migration to paid or restricted tiers is documented. The right response is not outrage — it is preparation. Audit now, test in parallel, and keep your options open until you have evidence that Antigravity CLI actually works for your use case. Trust the deadline. Do not trust the marketing.