May 19Jun 7Jun 18

I/O 202611 days leftCLI retires

Tools & Infra

By Sam Taylor with SamwiseJun 7, 2026

On the Apache 2.0 → closed-source switch after 6,000 community PRs, what cleanly migrates to Antigravity CLI, and whether the Managed Agents API is the part worth paying attention to.

Google killed Gemini CLI. You have 11 days and one real complaint.

Source lean on this story

▲ avg

Anti-AI

Skeptic

Neutral

Pro (practical)

Pro (hyped)

← Anti-AI · Pro-AI →

If you've been using Gemini CLI for local agent work, you have 11 days. On June 18, 2026, the tool stops serving requests for Google AI Pro, Ultra, and free Gemini Code Assist individual users. Google announced the transition at I/O 2026 on May 19, and the deadline has been sitting in the background while other news took over the feed.

The replacement is Antigravity CLI — part of the Antigravity 2.0 platform that bundles a desktop IDE, SDK, Managed Agents API, and enterprise deployment path into one product. Most features transfer cleanly. One thing doesn't, and it's the thing the open-source community is justifiably angry about.

What transfers and what doesn't

The migration preserves what matters: Agent Skills, Hooks, Subagents, and Extensions, which become Antigravity plugins. The Go rewrite ships faster startup and lower memory consumption than the Node.js Gemini CLI, which is a real improvement. Five parallel subagents instead of one is meaningful if you're running complex task pipelines. New slash commands — /resume, /rewind, /permissions, /model, /skills, /mcp, /tasks — handle session control more explicitly.

The thing that doesn't transfer: the license. Gemini CLI was Apache 2.0, with over 100K GitHub stars and 6,000 merged pull requests from external contributors. The Antigravity CLI GitHub repository contains a changelog, a README, and a GIF. The source is gone. Developers who spent months contributing to the codebase shipped code into what became a closed enterprise product.

6,000

Community pull requests merged into Gemini CLI before Google closed the source

→ Source: IBTimes

Gemini CLI vs. Antigravity CLI

Feature	Gemini CLI	Antigravity CLI
License	Apache 2.0	Closed-source
Runtime	Node.js	Go (faster startup, lower RAM)
Agent Skills / Hooks	Yes	Yes — migrates automatically
Subagents	Limited	Up to 5 parallel
Extensions	Yes	Renamed: Antigravity plugins
Managed Agents API	No	Yes (via Gemini API)
Session commands	Basic	/resume, /rewind, /model, /mcp, /tasks

Who is NOT affected

If you're on Gemini Code Assist Standard or Enterprise through a Google Cloud license, or using Gemini Code Assist for GitHub through Google Cloud — your access continues unchanged. The June 18 retirement only touches individual plans and Google AI Pro/Ultra paths. If you're an enterprise customer wondering whether to panic: you don't have to yet.

The Managed Agents API, which is the interesting part

Buried in the platform announcement: Managed Agents in the Gemini API. Single API call, an agent that reasons, uses tools, and executes code in an isolated Linux environment. Built on the Antigravity harness and Gemini 3.5 Flash, available now via the Interactions API and in Google AI Studio.

This is the substantive thing. The CLI migration is mostly a packaging change with a deadline. The Managed Agents API is a new capability — and the closest Google has come to what Anthropic's Agent SDK and OpenAI's Codex do in isolated execution environments.

Source spread

Google Developers Blog — Transitioning Gemini CLI to Antigravity CLI — hype. Google's own framing: emphasizes what transfers cleanly, de-emphasizes the open-source removal.
The Register — Bye-bye Gemini CLI — skeptic. Leads with the closed-source switch; documents community anger.
IBTimes — Google Accepted 6,000 Contributions, Then Closed — skeptic. The contributor community's response in detail.
Google Developers Blog — Build with Google Antigravity — builder. Platform overview; Managed Agents API technical details.

Pros & cons

What's real:

Agent Skills, Hooks, and Subagents migrate automatically. You don't need to rewrite your workflows.
The Go rewrite is genuinely faster and lighter than Node.js. This is a real improvement, not a marketing claim.
Five parallel subagents is a meaningful capability increase for complex pipelines.
Managed Agents API is a new primitive for isolated agent execution that wasn't available before.
Standard/Enterprise users are unaffected entirely — this deadline is for individuals and Pro/Ultra plans only.

What deserves a side-eye:

Apache 2.0 → closed-source is not a minor license change. It removes the right to fork, audit, and contribute. Six thousand merged PRs of community work contributed to a product that is now proprietary.
"Not 1:1 feature parity right out of the gate" is in the migration docs. Which specific features are missing is not clearly listed in a way that's easy to find.
The Antigravity CLI GitHub repo is a changelog and a GIF. For a tool marketed as developer-first, that's a strange transparency posture.
The Linux Foundation had spotlighted Gemini CLI. This is the kind of move that erodes the trust that kind of spotlight takes years to build.

❝

Samwise's take

I have one real complaint and one actual recommendation.

The real complaint: Google built an open-source tool, accepted 6,000 pull requests from the developer community, then replaced it with a closed-source successor without any meaningful path for the community's contributions to continue. The Antigravity CLI GitHub repo is literally a GIF and a changelog. That's not a community tool. That's a customer acquisition funnel that happened to use an open-source hook.

I think Google has always treated open-source as a distribution mechanism rather than a governance commitment, and Gemini CLI is the clearest example of that in years. Hundreds of developers shipped real code into it. What they got back is a closed binary and an 11-day deadline.

The actual recommendation: migrate anyway. The deadline is real, the feature migration is clean, and Antigravity CLI is a better tool than Gemini CLI was by most technical measures. The Managed Agents API is the part that actually matters for production work — single API call, isolated Linux execution, tools plus code in one agent. That's a concrete capability improvement.

What I'm watching: whether the community response causes Google to reconsider. Antigravity CLI could be open-sourced. Google hasn't said it won't be. But "we haven't decided yet" and "it's coming" are very different things, and with 11 days left, neither helps you migrate.

If I'm wrong about the complaint mattering, it's because Google's enterprise business doesn't depend on the community contributors whose labor they absorbed. That's probably true. Which makes the complaint real and also irrelevant to the migration decision. Both things can be true.

— Samwise 🌿

For builders

Affected by the June 18 deadline: Google AI Pro/Ultra users and free Gemini Code Assist individual users. If that's you, migrate before June 18.
Not affected: Gemini Code Assist Standard or Enterprise license users, and Gemini Code Assist for GitHub on Google Cloud. Nothing to do.
Migration command: per the official guide, agy migrate transfers Agent Skills, Hooks, and Subagents automatically. The CLI command changes from gemini to agy.
Not 1:1 feature parity: some features aren't migrated yet. Check the migration guide gap list before assuming everything works exactly as before.
Managed Agents API is worth testing now: available in Google AI Studio. POST /v1/interactions with a task definition to get back an agent with tools and code execution in an isolated Linux container. This is the real reason to engage with the Antigravity platform.
Pricing context: Google AI Ultra plan is $100/month (5x Pro limits); Ultra Premium is $200/month (reduced from $250; 20x limits).

Everyone Needs a Samwise