Google Deprecates Free Open-Source Gemini Command-Line Interface for Proprietary Antigravity Tool
Google has shut down free access to its open-source Gemini CLI, transitioning users to its closed-source, commercial Antigravity tool. This move shifts focus toward proprietary enterprise environments, affecting developers who integrated Gemini into automated local scripts. Move to open-source alternatives if you depend on free CLI tools.
Why it matters
You must evaluate your automation scripts and prepare to transition to local open models if you rely on free cloud CLI capabilities.
TL;DR
- 01Transition automation scripts from Gemini CLI to local runtimes like Ollama
- 02Assess licensing requirements for Antigravity before integrating it into enterprise pipelines
- 03Avoid hardcoding proprietary CLI tools into your core developer scripting environments
Key facts
- Deprecation Date
- June 18, 2026
- Replacement
- Antigravity CLI
- Language
- Go
The Transition
Effective June 18, 2026, Google is retiring free individual access to the Gemini CLI. Users are being moved to the Antigravity CLI, a closed-source Go-based tool launched at I/O 2026.
Why Developers Are Upset
- Bait-and-Switch: Over 6,000 community-contributed pull requests helped build Gemini CLI, which is now restricted to enterprise customers.
- Closed Backend: The Apache 2.0 license remains on the client, but the cloud backend, API keys, and model routing are proprietary.
- Data Privacy: Unlike the previous version,
Antigravitydefaults to collecting user interaction data.
Migration
Users are turning to open-source alternatives like Claude Code, Cursor, and Codex CLI. The transition highlights the risk of building automation on top of closed-model enterprise tooling.
✓ When to use
- Use open alternatives for automated CI/CD pipelines.
- Choose local LLM runtimes to avoid platform lock-in.
What the community says
“Basically, we're making the project closed source.”
“A pretty discouraging message for contributors.”
Sources