Google Stops Selling New Gemini Code Assist Subscriptions, Points Teams to Antigravity

Google has stopped selling new Gemini Code Assist Standard and Enterprise subscriptions. The change took effect on October 9, 2026, according to Google's own product documentation, and marks a shift in how the company packages AI-assisted coding for organizations. It does not mean every existing Code Assist account has been switched off. Instead, Google is directing future agentic coding purchases toward Antigravity within its Gemini Enterprise offerings while giving current subscribers a defined transition period.

The distinction is important for teams that use AI coding tools inside Visual Studio Code or JetBrains, especially those planning their next budget or expanding an existing deployment. A product can remain operational for current customers even after sales to new customers have ended. Google's published schedule separates new purchases, additional licenses, annual renewals and monthly renewals rather than treating them as one cutoff.

The dates existing customers need

New Gemini Code Assist Standard and Enterprise subscriptions can no longer be purchased as of October 9, 2026. Google says existing subscriptions continue to work and remain supported through the end of their contractual agreements. Customers can still add licenses until January 31, 2027; after that, adding seats is no longer supported under this path.

For annual subscriptions, auto-renewal can continue until January 31, 2027, after which annual renewals stop. Monthly subscriptions have a longer runway: Google says monthly auto-renewals can continue until December 31, 2027. These are distinct dates, so procurement teams should verify their current billing arrangement rather than assuming all accounts expire together.

The documentation also distinguishes the enterprise subscription changes from earlier shifts affecting individual users. In June 2026, Google stopped serving requests through certain Gemini Code Assist extensions and Gemini CLI for individual, Google AI Pro and Google AI Ultra tiers, directing those users toward Antigravity and Antigravity CLI. The October announcement concerns the commercial Standard and Enterprise subscriptions. Mixing those timelines could lead to incorrect guidance for developers.

Why Google is pointing to Antigravity

Google describes Antigravity as the direction for agentic coding assistance, available through eligible Gemini Enterprise editions. The idea is broader than a chat panel that suggests a function or completes a line of code: agentic tools are designed to carry out multi-step work across a project, subject to the permissions and controls the organization configures.

That positioning does not automatically establish feature parity for every existing Code Assist workflow. An IDE extension, command-line tool, organizational policy or deployment setting may have a different counterpart under Antigravity. Before committing to a migration, teams should inventory the features they actually use, including code completion, agent mode, repository access, security controls and usage reporting. They should then test those workflows against the replacement product in a controlled environment.

What Philippine developers and IT teams should do

For an individual developer working with a personal setup, first identify the exact product and account tier you are using. The words 'Gemini Code Assist' have covered multiple offers with different terms. Check the official release notes for the individual-user transition before assuming an enterprise deadline applies to your account.

For a business, the first step is administrative rather than technical. Record whether your subscription is annual or monthly, the contractual end date, how many licenses are assigned and whether the team expects to hire or add seats after January 2027. The second step is a pilot: choose a representative repository, confirm that the new tool can work with the organization's source-control and IDE setup, and document any gaps in policy enforcement or approvals.

Developers should also preserve a clear handoff for in-progress work. AI tools can help explain a codebase, but an agent's chat history is not a substitute for tests, issue tracking, architecture notes and a clean Git history. Keeping those artifacts independent of a particular coding assistant reduces migration risk.

What has not been announced

Google's public sunset page sets the commercial dates, but it does not promise identical pricing, performance or entitlements for every organization that moves to Antigravity. Teams should not assume that their old license automatically becomes a new one or that all developer integrations behave the same way. Confirm the plan and migration route with Google's official documentation or your account representative.

The immediate takeaway is not that Code Assist has disappeared overnight. It is that the purchasing path has changed, the renewal clock is now visible and teams have a finite period to plan a measured transition. For organizations using AI coding in production workflows, that is a reason to test early rather than scramble at the last renewal date.