If you searched "is Antigravity being deprecated?" — good news and bad news. The good news: Antigravity is not being retired. The bad news: Gemini CLI is, and Antigravity is what's replacing it. If you or your pipelines depend on the gemini command, you have until June 18, 2026 to do something about it.
This one moves fast and the naming is genuinely confusing, so let's untangle exactly what's changing, who it hits, and what to do before the deadline.
What's actually happening
At Google I/O on May 19, 2026, Google announced it's consolidating its developer tooling under one brand — Antigravity — and retiring the standalone Gemini CLI and the Gemini Code Assist IDE extensions in the process. The official word is in Google's own post, "An important update: Transitioning Gemini CLI to Antigravity CLI."
So the direction is the reverse of what a lot of people assume:
- Being retired: Gemini CLI and the Gemini Code Assist IDE extensions.
- The replacement: Antigravity CLI, a new agent that's part of the broader Antigravity platform.
Antigravity didn't come out of nowhere. It started in late 2025 as an AI-first IDE — a VS Code fork with strong multi-agent features powered by Gemini. In May 2026 it grew into Antigravity 2.0, an agent-orchestration platform that runs alongside your editor. The new CLI is the terminal front end for that same platform.
The deadline and who it affects
Here's the part to act on. On June 18, 2026, the legacy tooling stops serving requests for these tiers:
| Tier | What happens on June 18, 2026 |
|---|---|
| Google AI Pro | Gemini CLI + Code Assist IDE extensions stop serving requests |
| Google AI Ultra | Gemini CLI + Code Assist IDE extensions stop serving requests |
| Free Gemini Code Assist (individuals) | Gemini CLI + Code Assist IDE extensions stop serving requests |
| Gemini Code Assist for GitHub | No new installations accepted after this date |
There is no announced grace period. For affected accounts, the gemini command simply stops working that day.
Who keeps access
Enterprise customers are carved out. You're not forced to migrate immediately if you have:
- A Gemini Code Assist Standard or Enterprise license
- Gemini Code Assist for GitHub through Google Cloud
- A paid Gemini or Gemini Enterprise Agent Platform API key
Those accounts keep the legacy CLI working and continue getting the latest Gemini models — though Google still steers everyone toward Antigravity CLI eventually.
The CI/CD landmine
This is the part that bites teams, and it's why this matters beyond individual developers. Any automation that shells out to gemini on an affected tier breaks on June 18 — cron jobs, Git hooks, GitHub Actions workflows, deploy scripts, code-review bots, the lot. It fails silently in the sense that nothing warns you in advance; the command just stops returning results.
If you run anything unattended that calls Gemini CLI, treat this as a near-term operational task, not a someday-migration:
- Grep your infrastructure for
geminiinvocations across CI configs, scripts, and scheduled jobs. - Check which Google account each one authenticates as, and whether that account is on an affected tier or an exempt enterprise license.
- Migrate or re-license before the 18th.
A broken nightly job is annoying; a broken release pipeline on a Thursday is a bad day.
What Antigravity CLI brings
The replacement isn't just a rename. Antigravity CLI is built in Go (the old CLI was Node.js based), which Google says makes it "snappier and more responsive." The bigger shift is architectural: it's designed for asynchronous, multi-agent workflows — kicking off large refactors or multi-topic research that run in the background instead of locking up your terminal — and it shares its engine with the Antigravity 2.0 desktop app, so the CLI and the GUI drive the same agents.
Practically, it's a new binary you install fresh (distributed through Google's Antigravity download page and a GitHub organization), not an in-place upgrade of gemini. Plan for a real install-and-configure step, not a npm update.
What carries over
The migration isn't a from-scratch rebuild. Google says these remain compatible:
- Agent Skills
- Hooks
- Subagents
- Extensions — which carry over as Antigravity plugins
Your GEMINI.md project context, custom commands, and MCP server configs should map across too. "Should" is doing some work in that sentence, so test each one after you migrate rather than assuming a clean transfer.
Clearing up the Antigravity name confusion
Three different things share the "Antigravity" label, which is most of why people think Antigravity is the thing being killed:
- Antigravity IDE (1.0) — the original late-2025 AI-first IDE. It was effectively superseded by 2.0, and that overnight rollout broke some setups, which is where the "Antigravity is dead" chatter comes from.
- Antigravity 2.0 — the current agent-orchestration desktop app you run alongside your editor.
- Antigravity CLI — the new terminal agent replacing Gemini CLI.
So when you see "Antigravity is being deprecated," it's almost always someone referring to the 1.0 IDE being replaced by 2.0 — not the platform going away. The platform is very much the future Google is pushing developers toward.
How to migrate
For anyone on an affected tier, the path is straightforward but shouldn't wait:
- Install Antigravity CLI from antigravity.google/download and sign in with the same Google account you used for Gemini CLI.
- Follow Google's migration guide at antigravity.google/docs/gcli-migration to bring over your config, context files, and extensions.
- Update your automation — swap every
geminicall in scripts and CI for the new CLI. - Re-test the moving parts — MCP servers, hooks, skills, and any custom commands — before you rely on them.
- If you're enterprise, decide deliberately: stay on the legacy CLI under your license for stability, or adopt Antigravity CLI now for the new agent features. Just make it a choice rather than a surprise.
The bottom line
Antigravity isn't dying — Gemini CLI is, and June 18, 2026 is the date that matters. For individual and free-tier users the gemini command stops working; enterprise licenses get a reprieve. The replacement, Antigravity CLI, is a faster Go-based, multi-agent tool that keeps your skills, hooks, subagents, and extensions, but it's a fresh install and a real migration.
The single most important move this week is unglamorous: find every place your scripts and pipelines call gemini, and fix them before the deadline. Everything else can follow at your own pace — but that one can break production.