Google is shutting down Gemini CLI, its open-source AI coding agent, on June 18, 2026, and replacing it with Antigravity CLI, a closed-source rewrite that has ignited frustration among thousands of volunteer contributors. The original tool accumulated over 104,000 GitHub stars and merged more than 6,000 pull requests from external developers within roughly a year of its June 2025 launch. Now those unpaid contributors watch their work move behind an enterprise-only wall, raising questions about how tech companies treat open-source communities.

What Exactly Is Shutting Down on June 18?

The deadline applies specifically to consumer-tier users. Google announced that on June 18, 2026, Gemini CLI and Gemini Code Assist IDE extensions will stop serving Google AI Pro, Ultra, and free Gemini Code Assist users. Separately, no new organization installations of Gemini Code Assist for GitHub will be permitted from that date, and existing requests will stop being served in the weeks that follow.

There is one significant carve-out worth noting. Organizations with Gemini Code Assist Standard or Enterprise licenses, or those using paid Gemini or Gemini Enterprise Agent Platform API keys, will retain uninterrupted access to Gemini CLI. In other words, this is a consumer-tier shutdown, not an enterprise-wide one. Teams on enterprise licenses are not on a clock, though they may still want to evaluate Antigravity for new capabilities.

Why Did Google Replace an Open-Source Project That Was Working?

Gemini CLI launched in June 2025 as an Apache 2.0 licensed, TypeScript-based open-source AI coding agent. Within roughly a year, it became one of the more successful community efforts around an AI developer tool. The repository was even donated to the Linux Foundation before the shutdown announcement. Antigravity CLI is a Go rewrite of that Node.js codebase, and Google states the rewrite delivers faster startup times and lower memory consumption, though these claims have not been independently benchmarked.

The harder fact is the licensing change. Antigravity CLI's public GitHub repository contains only a changelog, a readme, and a GIF. No application code is visible. The tool is closed-source. Google's position is that the original Gemini CLI project "remains available to the community as an Apache 2.0 licensed repository with no changes." That is technically true but operationally hollow: the open repository is a skeleton that requires Google's proprietary backend to function. Without the API, the code does not run.

"Essentially working for free on a code base that will only be used in enterprises?" stated Andrea Alberti, a Gemini CLI contributor with 27 merged commits.

Andrea Alberti, Gemini CLI contributor

This sentiment captures the core frustration. Developers who spent unpaid hours improving an open project now watch that work move behind an enterprise-only wall. The pattern is one critics keep returning to: open a tool, harvest community contributions, then close the result. It stings more here precisely because the project was a Linux Foundation donation, not a casual side repository.

What Changes for Teams That Need to Migrate?

The migration itself is not technically insurmountable, but it carries hidden traps. For teams running Gemini CLI interactively, the switch is mostly an afternoon's work. For teams running it inside CI pipelines, cron jobs, or orchestration bridges, the problem is different: several failures are silent, meaning systems break without throwing errors.

The migration script does not touch automation, one Model Context Protocol (MCP) configuration field fails without throwing an error, and one widely used integration mode is not present at launch. The process involves installing the new agy binary, authenticating, importing plugins, moving skills, and rewriting MCP config. The expensive part is what breaks quietly.

Steps to Prepare for the Gemini CLI Shutdown

• Audit Your Usage: Determine whether your team uses Gemini CLI interactively, in CI pipelines, cron jobs, or orchestration systems. Silent failures are most likely in automated contexts.
• Check Your License Status: Confirm whether your organization holds an enterprise license or paid API key. If so, you are exempt from the June 18 deadline and can evaluate migration on your own timeline.
• Plan for Quota Changes: Gemini CLI offered 1,000 requests per day. Antigravity CLI uses a weekly compute-based cap. Heavy users report exhausting it fast and facing multi-day cooldowns, so re-budget workloads accordingly.
• Test MCP Configuration: The renamed MCP field (serverUrl becomes a different field name) fails silently. Test your configuration thoroughly before the cutoff date.
• Evaluate Alternatives: Consider whether to migrate to Antigravity, claim an enterprise exemption, or move off Google's tools entirely. The decision depends on your team's dependency on Google's backend and tolerance for closed-source tooling.

What Capabilities Are Lost or Changed?

The migration matrix reveals 15 dimensions that change between the two tools. Most agent skills, subagents, and plugins carry over or are simple renames. However, several capabilities either regress or disappear entirely.

Custom themes are not supported in Antigravity CLI with no estimated time for arrival. The ACP stdio mode, used by some teams for integration, is not present at launch. The quota system regresses from daily to weekly, and the configuration structure moves from ~/.gemini/ to ~/.gemini/antigravity-cli/. Most significantly, the license changes from Apache 2.0 open-source to closed-source, forcing teams to either accept the change or fork the old repository.

The strategic logic behind Google's move is defensible: the company wants a single shared agent harness across its CLI and desktop surfaces. But the communications were not. The migration would have landed far more cleanly with an explicit acknowledgement of the contributor question and a longer runway. For teams, the lesson is structural: treat any vendor-controlled "open" tool whose value depends on a proprietary backend as a managed dependency, not a true open-source one, and keep a migration plan warm.

The June 18 deadline is nine days away from the publication of this article. Teams still using consumer-tier Gemini CLI should begin their migration assessment immediately, particularly those running the tool in automated systems where silent failures pose the greatest risk.