Google stopped selling Gemini Code Assist on October 9. Your renewal date is the real decision date
New Gemini Code Assist Standard and Enterprise subscriptions ended October 9. Existing ones keep working, but seat additions and annual renewals stop after January 31, 2027.
Listen to this article · 4 min
AI-generated narration of the full article.
“Starting October 9, 2026, you can no longer purchase new Gemini Code Assist Standard or Enterprise subscriptions.” That line in Google Cloud’s documentation is the whole announcement. What it sets in motion is a procurement project with a fixed end date.
Nothing stops working today. Google’s sunset page says existing subscriptions “will continue to work and remain supported until the end of your contractual agreement.” The dates that matter come next.
The Gemini Code Assist sunset, by date
October 2026December 2027
- Oct 9, 2026No new Standard or Enterprise purchases
- Jan 31, 2027Last license additions; last annual auto-renewal
- Dec 31, 2027Last monthly auto-renewal
For an annual enterprise customer, January 31, 2027 is the practical decision date: after it, you cannot add seats for new developers and you cannot renew. Monthly subscriptions can auto-renew through December 31, 2027. Google directs customers toward Antigravity, which “is included in Gemini Enterprise editions,” and asks them to “plan your subscription transition to Gemini Enterprise.” Gemini CLI users get a migration guide to the Antigravity CLI, and Antigravity IDE extensions cover VS Code and JetBrains.
The successor is a different purchase
This is not a rename. Gemini Code Assist was bought as a coding assistant. Antigravity comes inside Gemini Enterprise editions, a broader suite license, and is positioned for agentic coding. That changes three things at once: who signs the contract, what the license covers, and what the tool is allowed to do on a developer’s machine.
An assistant that suggests code and an agent that edits files, runs commands and opens pull requests are different risk classes. The second is closer to what we described in agents as authors of production changes: its output enters the change process, and the controls belong there.
Four questions before January
Who is on which contract? List every Code Assist subscription by type (annual or monthly), seat count and end date. Teams that grew through card purchases or separate projects often surprise central procurement.
What did you configure that must be rebuilt? Admin settings, identity integration, logging, data handling terms and any code customization were set up for one product. Map each to its equivalent in the target tool, or record that there is none. Google’s page does not claim feature parity, and you should not assume it.
Is the new tool in the same risk class? If the replacement acts as an agent, decide where it runs, what it can execute, and who approves its changes before rollout, not after. Sandboxing, command approval and repository permissions are part of the migration, not a later hardening phase.
Is this the right moment to compare? A forced migration is the one time switching costs are already being paid. Run the candidates, Antigravity included, on your own repositories and tasks, with your own acceptance criteria, before the renewal conversation starts. Treat it like a model retirement: the interface you depended on is going away, and behavior, not just syntax, will change.
Gemini Code Assist customers have time. They do not have unlimited time, and the work that takes longest, evaluation and control mapping, is the work that cannot start in January.