Google Is Moving Many Gemini CLI Users to Antigravity CLI

Google Is Consolidating Its AI Coding Tools Around Antigravity

Google is preparing a major shift in its AI developer tooling: many users of Gemini CLI and Gemini Code Assist will be pushed toward Antigravity CLI, the company's newer agent-first development platform.

The change affects free users, Google AI Pro users, and Google AI Ultra users. Starting June 18, those groups are set to lose access to Gemini CLI, Gemini Code Assist IDE extensions, and Gemini Code Assist for GitHub unless they fall into the enterprise or API-key exceptions.

The replacement path is Antigravity CLI. Google describes it as a platform built for modern multi-agent workflows, with a server-side harness, a new terminal experience, and the ability to coordinate multiple background agents for more complex engineering tasks.

On paper, the positioning makes sense. Coding assistants are moving beyond single-turn autocomplete and chat into orchestration systems that can scaffold projects, answer questions, provision infrastructure, and run multi-step agent workflows. But the rollout is already creating friction among developers who preferred the openness and flexibility of Gemini CLI.

The Big Tradeoff: More Agent Infrastructure, Less Openness

Gemini CLI has been open source, with public code and a visible contributor base. Antigravity CLI is not following that same model, at least for now.

That matters because CLI-based coding tools are often customized heavily. Developers build wrappers, automation layers, hooks, local workflows, and team-specific conventions around them. Moving from an open-source CLI to a closed-source platform can break that trust, especially when the new tool does not yet match the old one feature-for-feature.

Google has acknowledged that Antigravity will not have full parity immediately. The company says key capabilities will be available through plugins, including Agent Skills, Hooks, Subagents, and Extensions. Still, for users who rely on the existing Gemini CLI ecosystem, that means a migration period with uncertainty.

Usage Limits Are Becoming the Flashpoint

The strongest early complaints are not just about openness. They are about quotas.

Some developers testing Antigravity CLI say they are hitting usage limits much faster than they did with Gemini CLI. That creates the perception that the new platform may be effectively more expensive or more restrictive, even for users already paying for Google's AI tiers.

This is part of a broader industry pattern. AI coding tools are getting more powerful, but agentic workflows consume more tokens and compute than simple chat or autocomplete. When a tool can plan, spawn agents, inspect files, revise code, and keep working in the background, the cost profile changes quickly.

That is why pricing and quota design are becoming just as important as model quality. Developers may tolerate a migration if the new tool is clearly better. They are less likely to accept it if the experience feels less open, less complete, and more constrained at the same time.

For more context on this shift, see our coverage of agentic AI's token cost problem and the broader move toward AI coding agents.

Enterprise and API-Key Users Get a Different Path

The cutoff is not universal. Enterprise users and developers using paid Gemini or Gemini Enterprise Agent Platform API keys are expected to keep access to Gemini CLI. Gemini Code Assist Standard and Enterprise license holders, along with users accessing Gemini Code Assist for GitHub through Google Cloud, are also expected to avoid the disruption.

That split is important. It suggests Google is not abandoning Gemini CLI entirely. Instead, it is narrowing the product's default availability while nudging mainstream users toward Antigravity.

For organizations, this may be manageable. Enterprise teams usually have procurement, licensing, and internal platform processes that can absorb a tool transition. For individual developers and smaller teams, the change feels more abrupt because the old workflow may simply stop being available unless they move to a different access path.

What This Says About the AI Developer Tool Market

Google's Antigravity move reflects a bigger change in coding assistants. The market is shifting away from lightweight, local-feeling tools toward managed agent platforms.

That has advantages. A unified platform can improve reliability, coordinate background work, update agent behavior centrally, and support more complex workflows. It also gives providers better control over cost, safety, telemetry, and product direction.

But the tradeoff is developer trust. Software engineers tend to value tools they can inspect, automate, and bend to their workflow. If agent platforms become closed, quota-heavy, and hard to customize, they risk alienating exactly the users who made the earlier tools valuable.

Antigravity CLI may still become a stronger long-term platform than Gemini CLI. The question is whether Google can make the migration feel like an upgrade rather than a lock-in event.

For now, the message to developers is practical: audit your Gemini CLI usage before June 18, check whether your account type keeps access, and test Antigravity early if your workflow depends on Google's coding tools.