100k stars · 6k+ PRs · June 18 cutoff · Antigravity replacement
Who is affected? Developers who shipped plugins, merged PRs, or wired SKILL.md workflows to Gemini CLI throughout 2025—then learned at Google I/O on May 19, 2026 that June 18 ends hosted access for free, Pro, Ultra, and most individual Code Assist paths, with a push toward closed-source Antigravity CLI. Takeaway: the repo stays Apache 2.0, but whoever controls auth and APIs controls the product. This article covers the timeline, policy matrix, Antigravity gaps, community backlash, industry pattern, a five-step playbook, and a remote Mac VNC acceptance checklist.
In June 2025 Google released Gemini CLI, a TypeScript terminal agent under Apache 2.0. Within a year the project passed 100,000 GitHub stars and accepted more than 6,000 merged pull requests from external contributors—metrics Google itself cited when announcing the transition.
At Google I/O 2026 the company introduced Antigravity CLI as a unified “agent-first” platform and stated that starting June 18, 2026, Gemini CLI and related IDE extensions would stop serving requests for Google AI free tier, Pro, Ultra, and most individual Gemini Code Assist users.
The fight is not whether the repository disappears. It is whether Google used open source to harvest community labor, then moved day-to-day utility behind enterprise gates and a proprietary successor. Outlets including The Register, The New Stack, TechTimes, and FOSS Force document widespread use of the term bait-and-switch in threads and GitHub Discussion #27274.
Sunk contribution: Contributors such as Andrea Alberti had large PRs merged on the same day personal access was effectively sunset.
Infrastructure lock-in: Forking code is easy; running models without Google credentials is not.
Replacement gap: Reported Antigravity free quotas and missing features diverge sharply from the Gemini CLI era.
Partner churn: Integrators including Dynatrace, Elastic, Figma, Shopify, and Stripe must replan dependencies.
| Date | Event |
|---|---|
| Jun 2025 | Apache 2.0 launch; community contributions open |
| Jun 2025 – May 2026 | 6,000+ merged PRs; 100,000+ stars |
| May 19, 2026 | Google I/O: Antigravity CLI; Gemini CLI restriction announced |
| May 23, 2026 | Backlash intensifies in press and GitHub |
| May 29, 2026 | Linux Foundation highlights isitopen.ai at Open Source Summit NA |
| Jun 18, 2026 | Personal subscription paths stop Gemini CLI API service |
Primary sources: Google Developers Blog.
| User cohort | After Jun 18, 2026 | Practical path |
|---|---|---|
| Google AI free | No Gemini CLI service | Antigravity CLI or another tool + paid API |
| Pro / Ultra | No Gemini CLI service | Watch Antigravity billing; compare Codex / Claude Code |
| Code Assist individuals | Cut off | Migrate configs and skills off Google auth |
| Code Assist for GitHub (personal new installs) | Blocked from Jun 18 | Enterprise cloud path or different CI integration |
| Code Assist Standard / Enterprise | Unchanged | Keep Gemini CLI; optional Antigravity trial |
| Paid Gemini / Enterprise API keys | Unchanged | CLI + your key decoupled from consumer sunset |
| Enterprise GitHub via Google Cloud | Unchanged | Per contract |
Citable fact #1: “Open source repo” no longer equals “free hosted inference” for personal Google accounts.
Google markets Antigravity as the single platform for multi-agent work, preserving Skills, Hooks, and Subagents (extensions become Antigravity plugins). Google also admits no immediate 1:1 feature parity. Community reports highlight:
| Dimension | Gemini CLI (era ending) | Antigravity CLI |
|---|---|---|
| License | Apache 2.0 | Closed source (replacement repo lacks full source tree) |
| Free quota (user reports) | ~1,000 requests/day class | ~20 requests/day class (~98% drop cited by users) |
| ACP / project memory | Community workflows built | Gaps reported (ACP, Markdown memory, Ctrl+C behavior) |
| Docs / maturity | One year of community docs | Rushed launch per press commentary |
| Enterprise | Can keep Gemini CLI | May use both—“consolidation” is softer for paying orgs |
Citable fact #2: Technical “single platform” rhetoric applies hardest to individuals, not to enterprise licensees.
FOSS Force quoted Christine Hall: Google did not revoke the open license—it shut the infrastructure that made the tool useful.
Contributor Andrea Alberti asked whether volunteers were effectively building an enterprise-only codebase for free.
Google’s narrative centers on multi-agent consolidation. Critics note enterprises may still run Gemini CLI alongside Antigravity—undermining a universal technical mandate.
Citable fact #3: In AI CLIs, runtime ownership beats repository ownership. Forks without API access are souvenirs, not products.
GitHub discussion threads turned sharply negative; some developers canceled Google subscriptions and moved to Claude Code or OpenAI Codex CLI. The Linux Foundation promoted isitopen.ai (Model Openness Tool) to score transparency, reproducibility, and usage rights—using this episode as a teaching moment.
Classic open source lets you fork and run. AI “open source” often means open code, private models, private auth. Combined with Google’s history of killing consumer products, confidence in long-term CLI promises was already low.
Citable fact #4: Evaluate tools with a checklist: license, auth path, shutdown history, and closed successor terms—not star count alone.
Separate code openness from service openness. Confirm whether you fall under API key or enterprise license exemptions in Google’s blog post.
Export configs: Back up .gemini, hooks, and custom skills. Port portable SKILL.md trees per agentskills.io so Cursor or Claude Code can load them.
Parallel pilots: Run Antigravity, Claude Code, Codex CLI, or Gemini CLI with your own paid API key for one week each on the same repo.
Score infrastructure risk: Does the replacement require the same OAuth lock-in? Any local-model path? Use isitopen.ai dimensions where relevant.
Accept on macOS with GUI when needed: OAuth callbacks, keychain, TCC, and Xcode still favor a real Mac session. Windows-first teams can use a rented VNC Mac for a 20-minute checklist (next section) before buying a Mac mini.
The Gemini CLI drama does not force a Mac purchase by itself. Migration targets often do: iOS signing, OpenClaw Gateway, browser MCP permissions, and IM QR pairing still need graphical macOS sessions.
| Scenario | SSH-only remote Mac | VNC graphical session |
|---|---|---|
| New CLI OAuth / device code | Sometimes enough | Safer for browser MFA |
| Xcode / keychain / signing | Often blocked | Recommended |
| OpenClaw permission prompts | Unreliable | Recommended |
| Compare two CLIs for one week | Config only | Side-by-side IDE + terminal |
20-minute acceptance checklist: (1) Connect VNC; (2) install target CLI and finish OAuth; (3) run one minimal codegen or commit flow; (4) if iOS is in scope, open Xcode and verify signing; (5) document log paths and credential cleanup.
Yes. Apache 2.0 remains. What ends for many users is Google-hosted auth and quota for consumer subscriptions—not deletion of source code.
Google claims conceptual continuity into Antigravity plugins, but parity is incomplete short term. Keep skills in vendor-neutral SKILL.md folders to reduce lock-in.
This article addresses ethics and trust, not legal advice. Apache 2.0 does not guarantee SLAs; review CLAs and terms before large contributions.
The Gemini CLI episode typifies cloud-native “open” AI tools: licenses protect forks, not tomorrow’s free inference tier. Durable defenses are portable configs, owned API keys, and explicit runtime dependency maps.
If you are piloting Claude Code, Codex, OpenClaw, or Gemini CLI with a paid key without a spare Mac, buying a Mac mini for a one-month evaluation often loses to hourly or monthly VNC rental: keep your primary OS, use a cloud Mac only for OAuth, Xcode, and agent acceptance, then decide long term.
Tools change; environments should stay optional. Use the remote Mac plans below to stage your migration with a graphical macOS node.