Antigravity CLI version 1.0.2 has been released with new privacy controls and bug fixes, according to Google software engineer Shengzhe Yao. This update follows the recent transition from Gemini CLI to the new platform on May 19, 2026.
Specifically, the new version allows developers to hide their email and plan tier by setting a specific environment variable. Meanwhile, the update resolves a bug where main agent tool permissions timed out after 60 seconds.
In addition, the update improves the help command to display full keyboard shortcuts. Consequently, developers can navigate the terminal interface more efficiently during active coding sessions. This improvement aims to simplify keyboard-driven workflows for remote SSH sessions.
Transition from Gemini CLI
Google is transitioning its terminal-based artificial intelligence tools under the new platform. Notably, the previous Gemini CLI and Gemini Code Assist extensions will stop serving requests on June 18, 2026, for certain tiers.
However, organizations using standard or enterprise licenses via Google Cloud will retain their access. The company stated that the previous project reached millions of users and over 100,000 GitHub stars.
Technical Features of Antigravity CLI
Built in Go, the Antigravity CLI offers faster execution on modern computers and supports asynchronous workflows. This terminal interface allows developers to run large-scale refactors without locking their active sessions.
Furthermore, it shares the same agent harness as the desktop application. This unified architecture ensures that all future improvements apply automatically across all platform surfaces.
Platform Ecosystem and Pricing
The platform now consists of four distinct surfaces, including the desktop application, the SDK, and the Antigravity CLI. Meanwhile, Google is deprecating the original IDE in favor of version 2.0.
Access to the full platform is available through the Google AI Pro tier for 20 dollars per month. Additionally, Google offers a new AI Ultra plan at 100 dollars per month with higher usage limits.
Developer Feedback and Future Outlook
Some developers have raised concerns regarding usage limits and the closed-source nature of the new tool. Nevertheless, the development team is actively working on documentation and code examples.
According to Shengzhe Yao, the next steps for the project include integrating community feedback and publishing tutorials. Developers can track these rapid updates directly through the changelog command.
Source: X (@shengzheyao) — researched
