Google Antigravity release notes: Gemini CLI gets a deadline

This is not another small IDE button. It is a deadline.

Google Antigravity is Google's agentic development platform for launching, monitoring and reviewing coding agents. A coding agent is an AI assistant that can read project files, propose changes and use tools inside the access you grant. Google's updated Gemini Code Assist release notes now say Gemini Code Assist IDE Extensions and Gemini CLI will stop serving requests for Individuals, Google AI Pro and Google AI Ultra on June 18, 2026. Google's advice is to migrate to Antigravity and Antigravity CLI before that date.

Source: Gemini Code Assist release notes and Code with Gemini Code Assist

Google Antigravity release notes: what changed?

The practical change is simple: if you use Gemini CLI or Gemini Code Assist as an individual user, through Google AI Pro or through Google AI Ultra, you need to plan for Antigravity CLI before June 18. Antigravity CLI is the terminal surface for Google Antigravity. It brings the same agentic idea into the terminal: multi-step reasoning, multi-file editing, tool calling and conversation history.

Google's developer blog also says Antigravity CLI will not have full 1:1 parity with Gemini CLI at launch. It does keep the main building blocks Google calls out: Agent Skills, Hooks, Subagents and Extensions, with extensions becoming Antigravity plugins. For Nordic teams, that means the migration is not just an install step. It is a short control exercise: which skills, hooks, subagents, plugins and MCP connections need to come over?

MCP, Model Context Protocol, is a way to connect AI tools to external systems through defined server profiles. An approval gate is a human checkpoint where the agent needs approval before changing files, running sensitive commands or moving on.

Source: An important update: Transitioning Gemini CLI to Antigravity CLI and Antigravity CLI overview

What to test before the Gemini CLI cutoff

Start with a small but real development folder, not a toy example. The point is to see what actually carries over.

• Check your license or user type. Google's cutoff applies to Individuals, Google AI Pro and Google AI Ultra. Standard and Enterprise customers are handled separately in the blog post, where Google says their access remains unchanged.
• Start Antigravity CLI in a project and let the first launch detect older Gemini CLI profiles if they exist. The migration guide describes an interactive checklist for extensions and global configurations.
• Look for local skills. If the project has .gemini/skills/, Google says the folder must be renamed or moved to .agents/skills/ for the Antigravity agent to recognize them as active slash commands.
• Review MCP configurations. Google says Antigravity CLI uses mcp_config.json, and that older keys such as url or httpUrl should become serverUrl for remote websocket or SSE servers.

Source: Migrating from Gemini CLI and Installation & auth

This is very much Tool Forge territory: do not rebuild the whole development workflow first. Make access, secrets, environment variables, scope, logs and approvals visible. Then the agent can do useful work without passwords, internal systems or production data ending up in a chat box.

Short example: use the new Antigravity feature

Human step: Install Antigravity CLI from Google's documentation. Then open a terminal in a non-critical project and launch Antigravity CLI with agy. Do this before pasting the prompt below.

Source: Getting Started with Antigravity CLI, Installation & auth and Migrating from Gemini CLI

Prompt to the agent after the project is open:

Inventory this repository for Gemini CLI migration to Antigravity CLI. Find GEMINI.md or AGENTS.md, .gemini/skills, MCP settings, hooks, extension references, and any project rules. Return a short migration checklist with files to rename, configs to convert, permissions to review, and tests to run. Do not change files yet.

Good output should:

• Separate verified files from assumptions.
• Call out .gemini/skills/, MCP profiles and plugins separately.
• Suggest concrete test commands or manual checks.
• Mark what a human should approve before the agent changes files.

What to watch next

The important thing now is not to chase every release note. It is to get a controlled transition before June 18 if your team uses Gemini CLI in an affected user tier. The next signal to watch is whether Google adds more migration fixes, plugin improvements or clearer Gemini CLI-to-Antigravity CLI parity notes to the Antigravity changelog.

Source: Google Antigravity Changelog and Google Antigravity Releases