Gemini Code Assist sales end: auto-renewal stops in 2027

Google stopped selling Gemini Code Assist today. As of October 9, 2026, new Gemini Code Assist Standard and Enterprise subscriptions can't be purchased, and existing ones stop auto-renewing in 2027. Google points everyone to Antigravity instead. If your team codes with Gemini Code Assist, you have roughly one budget cycle to decide what replaces it.

What actually happened

The Gemini Code Assist release notes carry the announcement under a plain heading: sale of Gemini Code Assist subscriptions is ending. The details:

• October 9, 2026: new Standard and Enterprise subscriptions can no longer be purchased.
• Through 2026: existing subscriptions keep auto-renewing.
• 2027: auto-renewal ends. Google hasn't published an exact cutoff date in that entry.
• The replacement: Google directs teams to Antigravity for AI developer tools.

This is the last step of a wind-down that has been running all year. On September 4, Google stopped new Code Assist sales through the Cloud console for billing accounts without an active subscription. In June, the Code Assist IDE extensions and Gemini CLI stopped serving the individual, Google AI Pro, and Google AI Ultra tiers, and those users were told to move to Antigravity and Antigravity CLI. The product overview now carries a notice that new subscriptions are unavailable.

Why the Gemini Code Assist shutdown matters for your business

A coding assistant feels like a commodity until it disappears. The seat license is the easy part to replace. The hard parts are what your team built around it: IDE configs, repo indexing, custom context, admin policies, and the habits of every developer who uses it daily.

Treat this like any vendor sunset:

1. Find the renewal date. Your 2026 renewal still happens. The one after it doesn't. That's your real deadline.
2. Don't default to the replacement. Antigravity is Google's answer, but this is the moment to evaluate it against Copilot, Claude Code, Cursor, and open-weight options on your own repos.
3. Keep your context portable. Put coding rules in files the repo owns (AGENTS.md, CLAUDE.md, MCP configs), not in a vendor admin panel. Then the next switch is a config change, not a rebuild.
4. Check the data terms. A new tool means new retention and training terms for your code. Read them before the pilot, not after.

Sources: Google Cloud: Gemini Code Assist release notes, Google Cloud: Gemini Code Assist overview.