Google Antigravity CLI Replaces Gemini Developer Platform — June 18 Migration Deadline

Google announced on June 9 that the Gemini CLI developer tool is being replaced by the Antigravity CLI developer platform with a mandatory migration deadline of June 18 — giving developers nine days to transition.

Antigravity CLI features:

• Native multi-model routing through a single endpoint (Gemini Ultra, Flash, specialized variants) • Built-in prompt caching and session persistence • Integrated tool use connecting directly to Google Cloud services without separate authentication

Additional announcements:

• TPU 8t: 3x training throughput over TPU 7 through hardware improvements to systolic array architecture • TPU 8i: Inference-optimized with throughput and cost efficiency prioritized over training flexibility • DiffusionGemma: Open-weight model using diffusion architecture enabling non-directional generation — can modify any part of a sequence rather than only completing left-to-right • Google Flow: Vibe coding environment with natural language project scaffolding and AI-managed test writing

The June 18 cutover is not a deprecation warning — it is a hard deadline. Developers who have not migrated will experience service interruption. The migration is non-trivial: Antigravity's authentication model, endpoint structure, and parameter schema differ from Gemini CLI in ways that require code changes, not just configuration updates.

Why It Matters: If you have production code using Gemini API or Gemini CLI, migration before June 18 is mandatory. DiffusionGemma's non-directional generation solves a real architectural limitation for editing and revision workflows.