gemini cli users now have an antigravity migration deadline
google says gemini cli and gemini code assist stopped serving consumer-tier requests on june 18, with antigravity cli replacing the old path. the agent stack is consolidating around bigger workspaces, not single-purpose terminals.
google has moved the consumer path for its coding assistant stack: Gemini CLI and Gemini Code Assist IDE extensions stopped serving requests for Gemini Code Assist for individuals, Google AI Pro, Google AI Ultra, and free individual users on june 18, 2026. The replacement path is Antigravity CLI.
what changed
the official developer blog frames Antigravity as the new home for the command-line workflow, while the Gemini CLI docs now carry a migration notice at the top of the changelog. google cloud's release notes say the same thing in enterprise-doc language: the tools have been unified into a single, multi-agent platform called Antigravity.
read that carefully. this is not just a rename. the center of gravity is moving from "a model in your terminal" toward an agent workspace with more orchestration around it. google is making the CLI one doorway into that workspace instead of the whole product.
the practical checklist
if your scripts still assume Gemini CLI access through an individual tier, treat this as a broken dependency until proven otherwise. check auth, update onboarding docs, and run a real migration smoke test: clone a repo, ask the new CLI for a small diff, run tests, and confirm the output lands where your team expects it.
the bigger lesson is vendor-proofing. keep prompts, repo instructions, and verification commands in version control so the workflow survives a tool rename. the model menu will keep moving; your shipping ritual should not.
for a starting point, pair the migration with a prompt that forces evidence before confidence.