Gemini Code Assist and Gemini CLI are shutting down for consumer tiers on June 18, 2026 — here's how to migrate to Antigravity

Update, 18 June 2026: Gemini Code Assist IDE extensions and Gemini CLI shut down today for consumer tiers — migration to Antigravity now active

The shutdown date covered in this article has now arrived. As of today, Gemini Code Assist IDE extensions and Gemini CLI have stopped serving requests for Gemini Code Assist for individuals, Google AI Pro, and Google AI Ultra tiers, with no grace period. The gemini command is broken for affected accounts right now. Any CI/CD pipeline, GitHub workflow, or script calling gemini on those tiers stopped working today. (Google deprecation page)

Gemini Code Assist Standard and Enterprise subscribers are not affected and retain full access.

One timing detail to note on GitHub: the consumer version of Gemini Code Assist on GitHub is deprecated today and blocks new installations, but the full shutdown of existing code review activity does not happen until July 17, 2026.

The replacement path described in the original article remains the same: install Antigravity CLI from antigravity.google, run agy plugin import gemini, rename GEMINI.md to AGENTS.md, and update any scripts referencing gemini to use agy. One meaningful change from the original story worth flagging: quota has shifted from 1,000 requests per day to a weekly compute-based cap, which heavy users are already reporting as a significant downgrade. (Google FAQs)

Update, 18 June 2026: Gemini Code Assist IDE extensions and Gemini CLI are shut down today for consumer tiers — migration to Antigravity is now mandatory

The deadline covered in this article has now passed. As of today, Gemini Code Assist IDE extensions and Gemini CLI have stopped serving requests for Gemini Code Assist for Individuals, Google AI Pro, and Google AI Ultra tiers. There is no grace period. The gemini command is broken right now for affected accounts, and the Login with Google option for IDE extensions and Gemini CLI has also been removed as part of the deprecation (official deprecation page).

CI/CD pipelines, GitHub Actions workflows, cron jobs, and any automation calling the gemini command on these tiers are failing today. Standard and Enterprise license holders, and those using paid Gemini API keys, are not affected.

If you have not migrated yet: install Antigravity CLI from antigravity.google, run agy plugin import gemini to bring over existing extensions, rename GEMINI.md to AGENTS.md, and move .gemini/skills/ to .agents/skills/. Update any scripts referencing gemini to use agy. The full migration steps are in the official migration guide.

Note that Antigravity CLI does not have full feature parity with Gemini CLI, and the quota model has changed from a daily request cap to a weekly compute-based limit, which heavy users are finding more restrictive.

Google has set a hard deadline. On June 18, 2026, Gemini Code Assist IDE extensions and Gemini CLI will stop serving requests for anyone on the Gemini Code Assist for individuals (free), Google AI Pro, and Google AI Ultra tiers. If you use any of these tools and fall into one of those tiers, your setup will simply stop working on that date. No grace period, no gradual wind-down.

The replacement is Antigravity and its companion Antigravity CLI, announced at Google I/O on May 19, 2026. That announcement opened roughly a 30-day migration window before the cutoff, so the clock is already running.

What exactly is being shut down

Three things stop working for affected users on June 18:

Gemini Code Assist IDE extensions (VS Code, IntelliJ, and the rest of the JetBrains family)
Gemini CLI (the gemini terminal command)
Gemini Code Assist for GitHub — no new installations on GitHub organisations from June 18, with requests stopping entirely in the weeks that follow

The affected tiers are the free individual tier, Google AI Pro, and Google AI Ultra. If you have a Gemini Code Assist Standard or Enterprise subscription through Google Cloud, none of this applies to you. Your access continues as normal.

Gemini CLI also remains available via paid Gemini and Gemini Enterprise Agent Platform API keys, so teams using it through Google Cloud infrastructure are similarly unaffected.

What Antigravity actually is

Antigravity has been building since late 2025 as an AI-first IDE, initially a VS Code fork with multi-agent features powered by Gemini. At Google I/O, Google announced Antigravity 2.0, repositioning it as a standalone desktop application built around agent orchestration rather than a traditional editor assistant.

The Antigravity ecosystem now includes:

Antigravity 2.0, a standalone desktop app for managing and running multiple agents in parallel
Antigravity CLI, a Go-based terminal tool invoked with the agy command rather than gemini
An Antigravity SDK and Managed Agents capability via the Gemini API
Enterprise support through the Gemini Enterprise Agent Platform

The framing from Google is a shift from IDE-centric code assistance toward multi-agent workflow management as the primary abstraction. Antigravity 2.0 supports scheduled tasks on cron schedules, dynamic subagents for parallelised work, project and worktree organisation, and integrations across Google AI Studio, Android, and Firebase.

What the migration actually involves

The core of the migration is straightforward: install agy, authenticate, and swap out your configuration. Most of it boils down to a binary rename and one environment variable change, from GEMINI_API_KEY to AV_API_KEY. Migration guides in the community are estimating around 45 minutes for a typical setup.

The parts that require more attention:

MCP configuration has a renamed field that will break quietly if you copy it across without checking
CI/CD pipelines and shell scripts that call the gemini command directly will need updating before June 18. Any pipeline that hits the deadline without being updated will fail with no fallback
Feature parity is not complete at launch. Google has said upfront that Antigravity CLI does not have 1:1 parity with Gemini CLI. Agent skills, hooks, subagents, and extensions are all supported in Antigravity CLI, but if you rely on specific Gemini CLI features, it is worth checking the current Antigravity CLI release notes before assuming everything carries over

The current Antigravity CLI release is v1.0.1. The last stable Gemini CLI release was v0.44.0.

The quota model is changing

This is worth understanding before you migrate. Gemini CLI offered 1,000 requests per day. Antigravity CLI uses a weekly compute-based cap rather than a daily request count. Some heavy users have reported hitting that cap quickly and facing multi-day cooldowns before it resets.

If you have a Google AI Pro or Ultra subscription, it automatically grants higher daily usage limits within Antigravity. For users on the free individual tier, Antigravity has its own individual plan with unpaid access, so you are not left without options, but the quota structure is genuinely different from what you may be used to.

IDE integration after the migration

For VS Code and JetBrains users, Antigravity CLI automatically detects existing editor installations through the Google AI extension and the Code Assist extension respectively. The integration in Antigravity 2.0 and Antigravity IDE is native and includes bidirectional session sharing via /export.

Cursor and Windsurf do not have official Antigravity integration yet as of the May 2026 announcement, but both support agy as a standard external terminal, so you can still use it alongside those editors.

What you should do before June 18

If you are on the free, Pro, or Ultra tier:

Check your pipelines and scripts for any calls to gemini. These need to be updated before the deadline or they will break.
Install Antigravity CLI (agy) and authenticate with your Google account. Your Pro or Ultra subscription carries over for quota purposes.
Review your MCP configuration carefully rather than copying it wholesale. The renamed field is the most common quiet failure in migrations.
Check the Antigravity CLI release notes for any features you depend on that may not have launched yet.

The official deprecation page and Google’s transition announcement are the authoritative sources for this change. Several community migration guides are also available if you want a step-by-step walkthrough of the agy install and configuration process.

June 18 is close. If Gemini Code Assist or Gemini CLI is part of your daily workflow, now is the time to make the switch.