On the morning of June 18, someone's CI pipeline quietly stopped working.

When the gemini command threw a "service has been discontinued" error, Gemini CLI was already gone. 100,000 GitHub stars, 6,000 merged pull requests — an open source tool built together by the developer community over a year had been replaced by a closed-source Go binary.

TL;DR
Gemini CLI shutdown → Open→Closed transition → Quota cuts → 5-step migration → Pick your alternative

Why did pipelines stop on June 18?

Google announced the Gemini CLI shutdown on May 19, declaring a forced migration to Antigravity CLI with the message: "Your workflows have outgrown those early days — it's the multi-agent era now."

The affected users are clearly defined: Google AI Pro and Ultra subscribers, free Gemini Code Assist users, and new GitHub Gemini Code Assist users. Enterprise customers with Standard or Enterprise licenses retain their existing access.

100K+
Gemini CLI GitHub Stars
6,000+
Community Merged PRs
30 days
Announcement to shutdown

Then on June 18, with no further warning, gemini stopped.

What Google took from the community

The sharpest criticism centers on open source strategy. Gemini CLI was published under Apache 2.0, and the community had merged over 6,000 pull requests to build it together. The Antigravity CLI repository, however, contains only "a changelog, README, and a GIF file." No source code.

The Register put it bluntly: "Google extracted value from open source contributions to build a proprietary replacement." The community sees it the same way — contributions made for free came back as a paid service.

"There won't be 1:1 feature parity right out of the gate."

— Google, Gemini CLI shutdown announcement

The quota situation got significantly worse too.

Gemini CLI (old)Antigravity CLI (new)
Quota model1,000 requests/day (24h reset)Weekly compute-based cap
Practical limit~1,000 requests per day~2,000 lines generated before exhaustion
When exceededResets next dayUp to 168-hour (7-day) lockout
Source codeApache 2.0 open sourceClosed source (binary only)

Unresolved security issue

According to Augment Code's analysis, an RCE (remote code execution) vulnerability was reported in Antigravity CLI in April 2026, with no confirmed patch as of June. Check the latest security advisories before deploying to production.

Several features are also missing from launch. The gemini --acp JSON-RPC interface is absent, and there's no official GitHub Actions integration. Discord, Slack, and Teams bridges require workarounds pending issue resolution.

Migrating to Antigravity CLI in 30 minutes

If your CI/CD is down right now, here's the sequence.

  1. Install Antigravity CLI
    macOS/Linux: curl -fsSL https://antigravity.google/cli/install.sh | bash
    Homebrew: brew install --cask antigravity-cli
    Windows PowerShell: irm https://antigravity.google/cli/install.ps1 | iex
  2. Authenticate & verify settings
    Run agy and complete the OAuth flow. Settings auto-save to ~/.gemini/antigravity-cli/settings.json. Run agy inspect to review all discovered configs.
  3. Migrate Extensions to Plugins
    Run agy plugin import gemini to convert existing Extensions to Plugins. Functionality is identical — just a rename.
  4. Move Skills directories
    Project skills: git mv .gemini/skills .agents/skills
    Context file: GEMINI.md → .antigravity.md
    Global skills: ~/.gemini/skills/ → ~/.gemini/antigravity-cli/skills/
  5. Rewrite MCP config (most critical)
    MCP settings move from inline settings.json to a separate mcp_config.json. Rename every remote server's url field to serverUrl. Missing this looks like a successful install but causes silent failures hours later during tool invocation.

Validate your migration

Run agy doctor to validate the full installation end-to-end. Also manually replace every gemini call in your CI/CD scripts with agy — the migration script won't do this for you.

When Antigravity quota runs out

Once the weekly compute cap is hit, you face up to a 7-day lockout. Google introduced a 5-hour priority refresh, but reports of 7-day lockouts affecting paid subscribers continued through May.

AlternativeKey featuresQuota model
Claude CodeFull MCP support, Anthropic nativePer-plan / API pay-as-you-go
DeepSeek V4Open source, OpenAI-compatible endpointDaily credit reset
GLM 5.1200K context, Apache 2.0Daily credit reset
Kimi K2.6262K context windowDaily credit reset

The key distinction is weekly reset vs daily reset. If lockouts are your problem, open source models with daily credit resets are a practical alternative. Claude Code, Cursor, and OpenCode all connect to these models via OpenAI-compatible endpoints.

Dive deeper

Google's Official Announcement The rationale for transitioning Gemini CLI to Antigravity CLI and what features are preserved developers.googleblog.com

The Register: In-depth Analysis Open source exploitation concerns and community reactions theregister.com

Full Migration Guide 5-step walkthrough, silent failure traps, and quota regression details digitalapplied.com

Antigravity vs Gemini CLI Comparison Security, compliance, and CI/CD support in detail augmentcode.com

Quota Lockout Alternatives Coding without week-long lockouts using open source models atlascloud.ai

Antigravity CLI Setup Guide (Korean) Installation to skill creation walkthrough elancer.co.kr