Google ends new Gemini Code Assist subscription sales

Google stopped selling new Gemini Code Assist Standard and Enterprise subscriptions on October 9, 2026. Its latest release notes close the remaining route for new purchases as Google directs developers toward Antigravity.

Existing subscriptions continue to work and remain supported until their contractual end, according to Google’s subscription sunset notice. Teams now have separate deadlines for buying more seats, renewing annual plans and renewing monthly plans.

Three changes with different deadlines

Customers can add licenses to existing subscriptions through January 31, 2027. Annual subscriptions can also renew automatically through that date. Monthly subscriptions can renew automatically through December 31, 2027. After the respective deadlines, those additions or renewals are unavailable. Google tells customers to plan their transition before the final renewal or contract end date.

The September 4 restriction was narrower. It stopped console purchases for billing accounts without an active Code Assist subscription, while leaving a route through Google Cloud sales. Accounts with existing subscriptions were unaffected by that restriction. The October notice closes new subscription sales more broadly.

A separate June 18 change stopped requests from the individual, Google AI Pro and Google AI Ultra tiers in Code Assist IDE extensions and Gemini CLI. Google explicitly places Standard and Enterprise subscriptions on their own deprecation schedule. These are different customer groups and different events.

What subscription owners can still change

The subscription administration guide remains relevant during the transition. An annual Code Assist commitment is billed monthly, so a monthly invoice alone does not establish that a customer has a monthly plan. Reducing the license count takes effect at the end of the current term, with the original count billed until then. Changing an annual subscription to monthly also waits until the annual term ends.

Subscription controls sit under Admin for Gemini and require billing administrator permissions or the documented combination of procurement order administration and billing viewer access. Turning off automatic renewal allows the subscription to expire at term end, when its licenses become invalid. Google says an expired subscription cannot be reenabled. These controls deserve review against the actual contract dates before a team changes its plan.

Antigravity access depends on the purchasing route

Google’s enterprise deployment guide describes two routes. A Google Cloud project and API connection uses consumption billing. A Gemini Enterprise Standard or Plus license provides included quotas and managed overages. Enterprise integration covers Antigravity 2.0, Antigravity CLI and IDE extensions. The guide specifically excludes the standalone Antigravity IDE from enterprise deployments.

For the subscription route, the AI developer tools requirements list paid or trial Standard and Plus subscriptions, plus paid Standard Emerging Market and Pay as you go editions. Emerging Market access has additional eligibility requirements. The project must use an invoiced Cloud Billing account receiving an active monthly invoice. Those prerequisites make billing setup part of the transition.

Administrators with an existing Gemini Enterprise subscription must enable developer tools for each location. Google lists the Discovery Engine API and Business AI Code API as required services. Enabling APIs alone does not grant access. A user still needs a Gemini Enterprise license and the Gemini Enterprise User role. Even someone with the Gemini Enterprise Admin role needs that separate user permission to use the tools.

Editor availability also needs a specific check. Google lists extensions for VS Code and Visual Studio, alongside JetBrains, Zed and Xcode. The latter three carry enterprise Preview labels in their individual entries. A team staying in its familiar editor therefore still needs to confirm the support status of its chosen integration.

Regulated deployments have another constraint. The same Google Cloud overview currently lists SOC 1, SOC 2, SOC 3, ISO certifications and FedRAMP among the certifications and controls Antigravity in Gemini Enterprise does not support. That published list makes a compliance review necessary for teams whose contracts depend on those requirements.

Included credits follow a shared weekly pool

The current quota guide lists AI developer tool credits equivalent to USD 10 per user per month for Standard and USD 15 for Plus. Google enforces these as a shared pool within each edition, project and location on a rolling seven day cycle. The weekly allowance is the monthly amount divided by four and multiplied by licensed seats. Unused credit does not carry into the following week.

Overages can keep usage running beyond included quota, but require an invoiced billing account and an active paid subscription. Trial subscriptions are ineligible. There is also an account specific exception. Google directs customers who received its email about overage billing controls launching August 17, 2026 to a separate legacy quota guide. The applicable billing rules need to be checked before comparing the replacement with a current Code Assist contract.

CLI migration includes configuration work

Google’s Gemini CLI migration guide describes an interactive first launch that detects legacy profiles and lets developers select extensions and global settings to convert. It also provides a command for importing older extensions as Antigravity plugins. Existing GEMINI.md and AGENTS.md workspace rules remain usable.

Custom workspace skills need to move to the .agents/skills/ directory. MCP server definitions use separate configuration files, and manually migrated remote WebSocket or SSE definitions need the updated serverUrl key. Google also warns that some custom terminal themes and experimental visual overlays may be unsupported. The documented migration covers real configuration changes, so a representative project with its actual skills and server connections is a useful place to validate the move.

For an existing customer, the practical starting point is the contract and renewal calendar. The engineering work then follows the chosen Antigravity surface, identity setup and billing route. Treating those as separate checks helps a team schedule the transition without confusing a sales deadline with the end of its current service.

Google Bay View complex in May 2022. Company context photograph by Dicklyon via Wikimedia Commons. Original photograph and website crops licensed under CC BY SA 4.0. Website layouts may crop the photograph.