Gemini CLI Is Now Enterprise-Only: What Every Developer Needs to Know

On May 19, 2026, Google stood on the Google I/O stage and announced that Gemini CLI — the open-source terminal agent that had attracted over 100,000 GitHub stars and 6,000 merged community pull requests in under a year — would stop accepting free-tier requests on June 18. Developers have 20 days to find a replacement or pay enterprise pricing. The successor, Antigravity CLI, ships without feature parity by Google's own admission.

This is not a deprecation notice. It is a full pivot: an Apache 2.0 project, built on community labor, captured by an enterprise tier. The developer community has been loud about what it thinks of that. Here is what actually happened and what you should do next.

What happened

Gemini CLI launched in June 2025 as a TypeScript-based, Apache 2.0 open-source terminal agent. Free access included 1,000 daily API requests — generous enough for serious daily use. The project grew fast: 100,000 stars, a pace of commits that put it in GitHub's trending repositories for weeks, and an unusually high ratio of external contributor PRs.

The pivot announcement came at Google I/O 2026. Starting June 18, free users, individual Google AI Pro subscribers, and individual Gemini Code Assist users all lose API access. Enterprise customers retain access to both Gemini CLI and the new Antigravity CLI. Non-enterprise developers are pointed to Antigravity CLI, which is closed-source, built in Go instead of TypeScript, and — by Google's own words — "won't have 1:1 feature parity right out of the gate."

The scale of the community bet

To understand why developers are angry, you need to see the numbers. In roughly eleven months of open development, Gemini CLI accumulated:

Each of those 6,000 pull requests represents developer time donated to a project under an open-source license. The contributors built integrations, fixed edge cases, wrote tests, and improved the CLI experience across platforms. Google received that labor for free, under the expectation of an open project.

What Antigravity CLI is (and isn't)

Antigravity CLI is the renamed, closed-source successor announced at Google I/O alongside Antigravity 2.0. It is built in Go, not TypeScript. It supports asynchronous multi-agent workflows and ships with cross-platform terminal sandboxing and credential masking. Those are genuine improvements over the original Gemini CLI architecture.

What it doesn't have yet: the feature surface that 11 months of community patches built into Gemini CLI. It was not available on standard package managers at launch. The weekly usage quota for individual users works out to roughly 2,000 lines of code before the cap kicks in — far less than the previous 1,000 daily requests.

# Official install path at launch
curl -sSL https://agy.google.dev/install | bash

# Verify install
agy --version

# If you had Gemini CLI aliases, update them:
# Old: gemini "explain this code"
# New: agy "explain this code"

The open-source bait-and-switch debate

The phrase "bait and switch" appeared in GitHub discussions within hours of the announcement. Contributor Andrea Alberti's comment — "we essentially worked for free on a code base that will only be used in enterprises" — was the most-quoted reaction, but the sentiment was widespread.

FOSS Force journalist Christine Hall put it precisely: the Apache 2.0 license remains technically intact, but the project's practical utility was cut off at the infrastructure layer. The code is still open. The API it depends on is not. An open-source project without open API access is a museum exhibit, not a tool.

The legal picture is clear: Google is within its rights. The ethical reading is why this landed hard. Community-sourced improvements shipped into a product that was then sold back as an enterprise feature. Whether this pattern discourages open-source investment in vendor-hosted CLI tools is a question the developer community will be answering for the next year.

Your migration options

There are four realistic paths forward, depending on your use case.

1. Antigravity CLI (free, limited)

The path Google intends. If your daily workflow stays within the weekly quota and you don't depend on TypeScript-extension compatibility, this is the lowest-friction swap. Expect rough edges for the first few months as parity gaps close.

2. Claude Code

The most-cited migration target in developer threads. Claude Code runs in your terminal, shares the same SKILL.md format as the broader agent ecosystem, and has a Pro plan ($20/month) with significantly higher context limits than Antigravity's free tier. See our Gemini CLI vs Claude Code comparison for a side-by-side feature breakdown.

# Claude Code install
npm install -g @anthropic-ai/claude-code

# Install the community migration skill from skills-hub
npx @skills-hub-ai/cli install gemini-cli-migration

# Start a session
claude

3. Codex CLI (OpenAI)

Now running on GPT-5.5 and switched to API-token billing in April 2026. Pay-as-you-go for Business and Enterprise. Strong option if you are already on the OpenAI API.

4. Locally hosted alternatives (Aider, Continue.dev)

Aider and Continue.dev work against local models or any OpenAI-compatible API. If the closure of Gemini CLI confirmed a preference for infrastructure you control, these are the options that don't depend on any vendor's free-tier decisions. Latency and capability trade-offs apply.

Practical migration steps

Before June 18, run through this checklist. It takes about 30 minutes for a typical workflow.

# 1. Audit all places you call gemini in scripts and CI
grep -r "gemini " ~/.zshrc ~/.bashrc ~/.config/ --include="*.sh" --include="*.yml" -l

# 2. Find any CI/CD pipelines using gemini
grep -r "gemini" .github/ .gitlab-ci.yml Makefile -l 2>/dev/null

# 3. List your Gemini CLI config to understand what skills/context you rely on
cat ~/.config/gemini/config.json 2>/dev/null || echo "no config found"

# 4. Install your replacement of choice
npm install -g @anthropic-ai/claude-code   # Claude Code
# OR
npm install -g @openai/codex-cli           # Codex CLI

# 5. Re-export any custom system prompts or scripts as SKILL.md files
# so they are portable across tools going forward

What this means for the CLI landscape

The Gemini CLI pivot is not an isolated event. It is the first major instance of a pattern that was always possible with vendor-hosted CLI tools: open the project, harvest community contributions, then restrict the infrastructure that makes the tool useful. That pattern is now documented and named.

The practical effect for developers choosing tools in 2026: free-tier infrastructure promises from large vendors carry more risk than they did twelve months ago. The Claude Code SKILL.md format, Codex CLI's open API billing, and locally-hosted Aider are not invulnerable to similar decisions — but they distribute the dependency differently. Anthropic does not run a free-access compute program that community contributions flow into. OpenAI's pay-per-use model means your cost scales with use rather than dropping to zero at a vendor's discretion.

For teams with critical Gemini CLI dependencies, the lesson is straightforward: write your AI coding workflows as portable SKILL.md files. A skill that runs on Claude Code today can run on Codex CLI or Antigravity CLI tomorrow. Vendor lock-in through workflow format is harder to break than vendor lock-in through API access — as June 18 is demonstrating.

Browse Claude Code alternatives or read the Gemini CLI vs Claude Code comparison to find the right fit for your workflow before the June 18 cutover.