Personal Gemini CLI ends June 18 as Google moves users to Antigravity

Google announced on May 19, 2026 that the personal and free paths for Gemini CLI will move to Antigravity CLI. The cutoff date is June 18, 2026. After that date, Google AI Pro and Ultra subscribers, free Gemini Code Assist for individuals users, and personal Gemini Code Assist IDE extension users will no longer send requests through the existing Gemini CLI path. Gemini Code Assist for GitHub also stops accepting new GitHub organization installs on June 18, with request service winding down over the following weeks.

That does not mean every Gemini CLI user is being shut off. Google says Gemini Code Assist Standard and Enterprise licenses remain supported. Gemini Code Assist for GitHub access through Google Cloud also remains available. Gemini CLI access through paid Gemini or Gemini Enterprise Agent Platform API keys continues as well. Personal and free developers received a migration deadline; teams with enterprise contracts or Cloud-backed access keep a supported route.

Google framed the change as more than a product rename. The same I/O 2026 developer announcement bundled Gemini 3.5 Flash, the Antigravity 2.0 desktop app, Antigravity CLI, Antigravity SDK, Gemini API Managed Agents, and Google AI Studio support for Android. Antigravity 2.0 is described as a central workspace for orchestrating multiple agents in parallel, creating dynamic subagents, running scheduled tasks, and connecting work across Google AI Studio, Android, and Firebase.

Gemini CLI began in 2025 as a way to use Gemini from the terminal. In the transition post, Google said the CLI had reached millions of users, more than 100,000 GitHub stars, over 6,000 merged pull requests, and hundreds of contributors. For a developer tool, those numbers are not a small experiment. They describe a working community surface with scripts, aliases, extensions, and workflows already built around it. The Antigravity transition is therefore closer to a platform consolidation than a routine CLI replacement.

The technical argument behind the migration is multi-agent work. Google says Gemini CLI usage has grown beyond the single terminal interaction pattern it originally served in 2025. Antigravity CLI is written in Go, aims for faster execution, supports background asynchronous workflows, and shares the same agent harness as the Antigravity 2.0 desktop app. That shared harness is the distribution layer Google wants to use for future agent improvements across terminal, desktop, and API surfaces.

The migration risk is compatibility. Google explicitly says Antigravity CLI does not immediately offer 1:1 feature parity with Gemini CLI. It names Agent Skills, Hooks, Subagents, and Extensions as important capabilities, but Extensions become Antigravity plugins. Developers who built wrappers, custom commands, workflow glue, or CI helpers on top of Gemini CLI need to treat this as a real migration, not just a binary rename.

For developers, the first practical checklist is authentication and quota. In the r/GeminiCLI transition thread on Reddit, users asked whether Antigravity CLI is open source, whether custom layers built on Gemini CLI will survive, whether Pro and free quota merge into the new product, and whether usage limits are lower. Some reported authentication URL issues after installing Antigravity CLI. Others said the visible quota appeared different from what they expected under Gemini CLI. These comments are not primary documentation, but they identify the migration failures users will measure first.

Google has not closed that feedback loop yet. The transition post points users to the Antigravity CLI community forum for feature requests and feedback. The request for feedback should be read alongside the no-feature-parity warning. Google has opened the migration window and announced the cutoff, but the notice itself does not prove that every personal workflow has a clean destination.

Antigravity 2.0's direction is clearest when paired with Gemini API Managed Agents. Google describes Managed Agents as agents launched with a single API call, running reasoning, tool use, and code execution inside an isolated Linux environment. It also says each interaction can connect to an environment that preserves files and state. The CLI becomes the terminal surface for that infrastructure, while the SDK and API let teams connect the same harness to products and automation.

The Gemini 3.5 Flash model card gives the platform story more context. DeepMind listed May 2026 results including 76.2% on Terminal-bench 2.1, 55.1% on SWE-Bench Pro Public, 83.6% on MCP Atlas, 56.5% on Toolathlon, and 78.4% on OSWorld-Verified. If Antigravity is meant to be an agent-first platform, the CLI migration is less about advertising a stronger model and more about aligning the runtime, tool permissions, persistent environment, and distribution surface around that model.

The difference from OpenAI Codex CLI or Anthropic Claude Code is the boundary between personal subscriptions and Google Cloud. Personal and free users must move to Antigravity, while enterprise contract users can continue using Gemini CLI. That split shows how agentic coding tools can have different lifetimes depending on whether they are sold as consumer productivity tools or controlled enterprise surfaces. A CLI's support policy now depends on cost, quota, data boundary, Cloud project linkage, and API key route.

For open-source contributors, the reported adoption metrics leave a harder question. Google cited more than 100,000 stars and 6,000 merged pull requests as evidence of Gemini CLI's success. Those numbers also highlight how much community-built workflow is being asked to move onto a new product surface. Unless Google quickly clarifies Antigravity CLI's source model, plugin migration guide, quota table, and compatibility matrix, contributors may see the success metrics before they see a reliable migration plan.

Teams should check four things before June 18. First, search for scripts, aliases, and CI jobs that invoke Gemini CLI directly. Second, verify whether existing extensions can move into Antigravity plugins. Third, decide whether experiments running through personal Google AI Pro or Ultra accounts should move to an enterprise license or a Google Cloud project. Fourth, run dry tests for quota and model availability so the new path does not break cost assumptions during real work.

Small personal projects may only hit installation and authentication issues. The risk grows for developers who use a terminal agent alongside Claude Code, Codex, Cursor, internal MCP servers, and repository automation. If Gemini CLI currently acts as a fast exploration agent, long-context question tool, repository scanner, or shell-command wrapper, Antigravity CLI's background workflow and plugin model need to be tested in that exact role. Since Google emphasizes asynchronous workflows, users should inspect failure logs, retry behavior, permission boundaries, and credential masking before focusing on convenience.

This announcement also matters outside the United States because personal or free CLIs often enter teams as informal experimentation tools. After June 18, 2026, that path changes to Antigravity. Internal onboarding documents, security review notes, MCP connection examples, shell aliases, pre-commit hooks, and GitHub Actions workflows written for Gemini CLI may produce different results before and after the cutoff.

Google gains a cleaner product architecture. If the Antigravity 2.0 desktop app, Antigravity CLI, Antigravity SDK, and Gemini API Managed Agents share one harness, Google can move the roadmap through one runtime. Model updates such as Gemini 3.5 Flash can reach CLI and API surfaces in a more consistent form. The I/O announcement path from Google AI Studio to Antigravity, Android, and Firebase also matches that integration strategy.

Users may lose some of the composability that made an older CLI useful. A simple Unix-style command line surface is easy to wrap, script, and combine with other tools. Antigravity CLI may provide a stronger agent harness, but closed quota rules, authentication changes, plugin packaging, or unclear source availability can reduce that composability. The migration needs evidence that existing workflows still work, not just a statement that the new CLI is faster and written in Go.

The June 18 decision is therefore an operations boundary, not a preference poll. Personal and free Gemini CLI usage should no longer be treated as a durable dependency. Enterprise and Cloud-backed teams can preserve the old Gemini CLI path, but new agent features are likely to land first inside the Antigravity harness. Individual developers should test Antigravity CLI while comparing the cost, permission model, and automation fit of Claude Code, Codex CLI, Cursor, and other alternatives.

The concrete change is where the terminal agent lives. In 2025, Gemini CLI brought a model into the shell. In 2026, Antigravity CLI brings the shell into Google's agent platform. The June 18 cutoff is the date when that difference reaches personal developers' shell history, wrappers, and CI jobs.

Sources

• Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI.
• Google The Keyword: Developer highlights from I/O 2026.
• Google The Keyword: Build managed agents with the Gemini API.
• Google DeepMind: Gemini 3.5 Flash Model Card.
• Reddit r/GeminiCLI transition reaction.