Gemini Code Assist Sales End: Renewal Dates and Options

Google stopped selling new Gemini Code Assist Standard and Enterprise subscriptions on October 9, 2026. Existing customers can keep using their subscriptions until the end of their current contractual agreement, but license additions and renewal options have different deadlines. Google points customers toward Antigravity for future agentic coding assistance, through eligible Gemini Enterprise editions.

What changed on October 9?

The Google Cloud documentation now says new Gemini Code Assist Standard and Enterprise subscriptions can no longer be purchased from October 9, 2026. This is a change to subscription sales, not a statement that every existing installation stopped working on that date. Google's page says current subscriptions remain supported until the end of each contractual agreement.

The deadlines are not identical for monthly and annual customers. Check the renewal date and contract terms for your own organization rather than assuming every plan ends at the same time.

Key dates for existing customers

These are the dates on Google's current sunset page. Your contractual end date may be earlier or later, depending on the agreement. Confirm the exact account status with your Google Cloud administrator or account representative before making a migration decision.

What happens if your team already uses Gemini Code Assist?

Google says existing subscriptions continue to work and remain supported until the end of the contractual agreement. That gives teams time to plan, but it does not mean that every future renewal or license increase will be possible. The January 2027 license-addition deadline matters for organizations that expect to expand their developer seats.

Make an inventory before you change anything:

1. Record the subscription type, renewal date, contract end date and number of assigned licenses.
2. List the IDEs, extensions, command-line tools and team workflows that rely on Gemini Code Assist.
3. Identify any shared prompts, project rules, custom integrations or internal documentation that need a replacement.
4. Test the replacement with representative code tasks, private repositories and the same review rules used today.
5. Confirm pricing, access controls, data handling and support terms before approving the change.

What is the suggested replacement?

Google's sunset page says agentic coding assistance will be available through Antigravity, which is included in Gemini Enterprise editions. It recommends planning a transition to Gemini Enterprise before the current plan reaches its final renewal or contract end date.

Do not assume this is an automatic, one-click migration or that every Gemini Code Assist feature has an identical replacement. The page does not provide a full feature-by-feature parity table, nor does it state that existing Code Assist subscriptions automatically convert to Gemini Enterprise. Review the current Antigravity IDE and CLI documentation, test the tasks your team relies on, and ask Google to confirm any commercial or support details that are not covered in the public notice.

Google also links a migration guide for moving from Gemini CLI to Antigravity CLI. That guide can help with the command-line transition, but it should not be treated as proof that every part of a Standard or Enterprise subscription migrates automatically.

How to plan the transition safely

Start with a small pilot rather than switching the whole team at once. Choose a few common tasks such as explaining a function, writing a unit test, debugging a build and making a contained refactor. Compare the result with your current workflow and check whether repository access, code review, command execution and team policies still work as expected.

Keep human review in place during the pilot. Coding agents can produce incorrect patches, use tools in unexpected ways or miss project-specific requirements. Require a diff review and tests before merging, and avoid granting a replacement tool broader permissions simply to make it work like the old setup.

For context on Google's broader work-agent direction, see our coverage of the Gemini agent announced for enterprise work. It is a separate product announcement, not a substitute for checking the specific Code Assist transition terms.

What remains unclear?

The sunset notice gives the key sales and renewal dates, but it does not settle every customer's commercial situation. Public documentation does not establish a universal migration deadline for every contract, a direct automatic conversion path, or exact feature parity between Code Assist and Antigravity. Pricing and access through Gemini Enterprise depend on the applicable edition and agreement. Confirm those details before changing licenses or ending a contract.

Frequently asked questions

Will Gemini Code Assist stop working on October 9, 2026?

Google says existing subscriptions remain supported until the end of the contractual agreement. October 9 is the date new Standard and Enterprise subscriptions stopped being sold.

Can an existing customer add licenses after January 31, 2027?

Google's page says new licenses can be added until January 31, 2027. After that date, no new licenses can be added under this sunset arrangement.

Is Antigravity a free replacement?

The notice says Antigravity is included in Gemini Enterprise editions. It does not say that every customer receives the same features or price as their former Code Assist plan.

Sources

• Google Cloud documentation: Gemini Code Assist Standard and Enterprise subscription sunset (last updated October 9, 2026).
• Google Cloud documentation: Gemini for Google Cloud release notes (October 9, 2026 entry).
• Antigravity: Gemini CLI migration guide.