Google kills Gemini CLI: what the Antigravity bait-and-switch means for teams picking AI coding tools

Google shut down the free open-source Gemini CLI on June 18, 2026 and replaced it with a closed-source rewrite called Antigravity CLI. For CTOs and product leads evaluating which AI coding tools to commit to, the episode is a useful case study in platform risk.

On 18 June 2026, Google shut down the free tier of Gemini CLI — the open-source terminal AI agent it had launched to compete with Claude Code and OpenCode — and replaced it with something called Antigravity CLI. The replacement is a closed-source Go rewrite. It doesn’t have feature parity at launch. The community’s response, as documented by the Linux Foundation and covered across developer forums, has been blunt: a “sickening bait-and-switch.”

What happened

Gemini CLI launched as an open-source project with a generous free tier: 60 model requests per minute, 1,000 per day, access to Gemini 2.5 Pro’s one-million-token context window. It accumulated a significant developer following quickly — not least because the free allowance made it genuinely usable for real work without a subscription.

The June 18 shutdown affects free, Pro, and Ultra users alike. Continued access requires a paid Gemini Enterprise Agent Platform API key. The replacement — Antigravity CLI — is closed-source, not yet at feature parity, and carries none of the naming or community continuity of the product teams adopted.

The platform risk lesson

This episode is a clean example of a pattern worth understanding before committing workflows to any AI tool: free tiers and open-source positioning are often subsidies to acquire users. They can be changed unilaterally once adoption is established.

That’s not a reason to avoid all commercial AI tools — most of the best development tooling in 2026 is commercial. But it’s a reason to think about how embedded a tool becomes before the terms shift. A development team that’s spent months building workflows around Gemini CLI now has to absorb either migration costs or a new payment obligation.

Questions worth asking before committing to an AI coding tool

The teams least affected by the Gemini CLI shutdown were those using provider-agnostic harnesses — tools like OpenCode that route to multiple model providers and don’t build workflow lock-in around a single vendor’s CLI. When one provider changes terms, swapping the model out is a config change rather than a migration project.

Platform risk in AI tooling is real and 2026 is still early enough that the landscape is shifting fast. The Antigravity episode is a useful reminder to build in resilience before you need it.

We cover which AI development tools we use in production on our AI-assisted development page.

← All research

More research.

VS Code 1.145 lets Copilot run local automations on a schedule with custom agents

GitHub's 6 November 2026 Copilot weekly release adds cron-scheduled local automations with custom agents in VS Code 1.145, alongside Copilot in JetBrains Air and a unified Copilot CLI settings dashboard.

Read ›

@GitHub in Slack and Teams is generally available: from a chat message to a pull request

GitHub's 6 November 2026 release makes @GitHub in Slack and Teams generally available, letting teams investigate bugs, create issues and open pull requests with an AI coding agent from a chat conversation.

Read ›

GitHub secret scanning cuts false alarms for AWS, Google and Alibaba cloud keys and adds a SpaceX detector

GitHub's 5 November 2026 secret scanning update tightens detectors for AWS, Google Cloud and Alibaba keys, relevant to teams building software with AI coding tools that can paste credentials into code.

Read ›

GitHub's Copilot code review can now be managed by API, with review effort levels and AI credit costs shown

GitHub's 6 November 2026 update lets organisations manage Copilot code review by API and see the review effort and AI credits each AI code review used, a sign AI-assisted development is becoming auditable.

Read ›

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work