Antigravity CLI is now the tool millions of developers must learn, whether they planned to or not.

By Blumefield | June 18, 2026

The Day a Beloved Tool Goes Quiet

For a swath of the developer world, June 18 will be remembered as the day a favourite tool went silent. As of today, Google stops serving requests from Gemini CLI and the Gemini Code Assist IDE extensions for everyone on its Google AI Pro and Ultra plans, along with those using the free individual tier. In its place, the company is pushing every one of those users toward Antigravity CLI, the terminal experience baked into its new agent-first development platform.

The numbers behind Gemini CLI explain why this matters. Since shipping in 2025, the tool gathered more than 100,000 GitHub stars, absorbed roughly 6,000 merged pull requests, and pulled in hundreds of community contributors. Google itself describes a user base in the millions. Tools with that kind of gravity rarely get retired, which is exactly why the Antigravity CLI handover is drawing attention well beyond the usual circle of early adopters.

Google frames the move as a response to how developers actually work now. The pitch is blunt: single-agent terminal sessions have been outgrown, and the future belongs to multiple agents passing work between each other against a shared backend. Rather than bolt that capability onto an aging codebase, the company decided to concentrate its energy on one platform. The result is a clean break, and a deadline that arrived faster than many expected when the plan was first announced at Google I/O in May.

What Antigravity CLI Actually Changes

The headline difference is architecture. Antigravity CLI is built in Go, which Google says makes it noticeably snappier and more responsive than its predecessor. Underneath, it shares the same agent harness as Antigravity 2.0, the standalone desktop application that anchors the wider ecosystem. That shared foundation means improvements to the core agents propagate everywhere at once, whether a developer is working in the terminal, the desktop app, or through the software development kit.

The more substantive shift is asynchronous, multi-agent orchestration. Where the old tool largely locked up a terminal session while it worked, Antigravity CLI can dispatch several agents to grind through tasks in the background. A developer can kick off a large-scale refactor, research three separate topics, and keep typing without waiting for any single job to finish. For teams running complex codebases, that change alone reframes what the command line is for.

Google has been careful to carry over the features people actually used. Agent Skills, Hooks, Subagents, and the old extension system, now rebranded as Antigravity plugins, all survive the migration. The company concedes there is not full one-to-one feature parity at launch, a rare admission that the transition will involve some friction. Still, the core jobs that drew people to the original tool, from grounded quick answers to scaffolding new projects to provisioning cloud infrastructure, remain on the table. The full migration details sit in Google's own developer documentation.

The Agent IDE War Heats Up

None of this is happening in a vacuum. The retirement of Gemini CLI lands in the middle of an intensifying battle over the agentic development environment, a market where the terminal has unexpectedly become the front line. Competitors are circling the same prize, and Google's decision to consolidate is a defensive and offensive move at once. A fragmented set of tools is easier to pick off than a single, deeply integrated platform.

The stakes are visible in the rest of the I/O announcements. Antigravity 2.0 ships with dynamic subagents, scheduled background tasks, and integrations that reach across Google AI Studio, Android, and Firebase. The platform runs on Gemini 3.5 Flash, which Google claims outperforms the earlier Gemini 3.1 Pro across almost every benchmark while running four times faster than rival frontier models. Speed, in an agentic world where dozens of calls fan out in parallel, is not a vanity metric. It is the difference between a tool that feels alive and one that stalls.

There is a commercial edge here too. Google paired the platform launch with a new $100 a month AI Ultra plan offering five times the usage limit of the Pro tier inside Antigravity. As the major labs race to convert free experimentation into recurring revenue, bundling the most capable agent experience behind a premium subscription is a familiar play. For more on how the broader AI tooling landscape is shifting, readers can follow ongoing coverage at Blumefield.

Enterprise Gets a Reprieve, Individuals Get a Deadline

The cutoff is not uniform, and the split tells its own story. Organisations using Gemini CLI or the IDE extensions through a Gemini Code Assist Standard or Enterprise licence, or through Google Cloud, keep their access unchanged. For them, Gemini CLI continues to receive the latest models and updates, and it remains reachable through paid Gemini and Gemini Enterprise Agent Platform API keys. Enterprises move on their own timetable, not Google's.

Everyone else faces a harder line. Individual users on Pro, Ultra, and the free tier lose service today. Gemini Code Assist for GitHub stops accepting new installations on organisations as of June 18, with existing request handling winding down over the following weeks. The asymmetry is deliberate. Google can afford to nudge individual developers abruptly because the switching cost for one person is low, while large customers with entrenched workflows need contractual certainty before they will budge.

That two-speed approach is becoming a pattern across the industry. The frontier of capability ships first to individuals who tolerate churn, while the stable, supported version lingers for the enterprises that pay the largest bills. The official timeline and the reasoning behind it are laid out in Google's migration announcement, which doubles as a roadmap for what the company expects developers to do next.

What Developers Should Do Now

For anyone still running Gemini CLI as a daily driver, the practical answer is simple: the time to move was yesterday, and the second-best time is today. Antigravity CLI is already available to everyone through the Antigravity download, and Google has published technical guides to smooth the path, with video walkthroughs promised in the coming weeks. The plugin and skill conventions are close enough to the old system that most personal setups should port over with modest effort.

The deeper question is strategic. Adopting Antigravity CLI is not just swapping one binary for another. It means committing to Google's vision of software built by fleets of cooperating agents rather than a single assistant answering one prompt at a time. That is a meaningful bet on a particular future, and developers who prefer a lighter, more neutral terminal may bristle at being herded onto a heavier, more opinionated platform. The full scope of the ecosystem is detailed on the Antigravity site.

Whatever the reservations, the direction of travel is unmistakable. Google has decided that the agent-first platform is the product, and the standalone terminal tool was a stepping stone. With Gemini CLI going dark today, the company is forcing a conversation it clearly believes it can win. The developers now migrating to Antigravity CLI will be the ones who decide whether that confidence is justified.