Google ends new Gemini Code Assist subscriptions and sets renewal deadlines

The October 9 change gives existing customers a transition period. Annual and monthly plans have different deadlines.

An intact green architectural bridge connects an older ochre platform to a new structure where patterned modules are being fitted.
Original AI-generated editorial illustration of a planned migration. Conceptual artwork, not an official Google image.

Google stopped selling new Gemini Code Assist Standard and Enterprise subscriptions on October 9, 2026. Its release notes point developers toward Antigravity through eligible Gemini Enterprise offerings. [G1]

For teams that already use Code Assist, the useful question is when their own agreement ends. Google says existing subscriptions remain operational and supported for their contracted term. [G2]

Check the renewal deadline and the contract end date before setting your migration timetable.

Editorial highlight · Original line from this article, not a third-party quotation.
Ochre and blue planning strips end at separate green tabs while a longer green strip continues beyond both, beside drafting tools.
Original AI-generated editorial illustration distinguishing renewal checkpoints from contract duration. Positions and lengths are symbolic and do not encode actual dates.

The dates to check

Additional licenses and annual automatic renewals remain available through January 31, 2027. Monthly automatic renewals continue through December 31, 2027. After the respective deadlines, those options close. [G2]

A renewal cutoff and a contract end date answer different questions. Teams should record both before deciding when to move. The appropriate transition timetable depends on the agreement they actually have.

What to review before switching

Start with a short inventory: who uses the tool, which editors they rely on, what access the assistant has, and which everyday tasks would be disrupted by a change. Ask the account administrator to verify the current billing cycle and contract terms.

For teams that also use Gemini CLI, Google's migration documentation covers extensions, skills and MCP configuration. That makes it worth reviewing the technical setup separately from the subscription decision. [G3]

Before committing to a replacement, compare its quoted cost, access controls and compatibility with the team's workflow. A small trial using non-sensitive sample code can help identify missing settings or integrations without making the next project deadline the migration test.

The practical priority is to choose an owner and a transition date early enough to leave room for testing. Existing customers should use their remaining contract period to make that decision deliberately.

Sources and references

Got a different take? I’d love to hear it. hello@maisfps.com

Join the conversation

O seu endereço de e-mail não será publicado. Campos obrigatórios são marcados com *

Este site utiliza o Akismet para reduzir spam. Saiba como seus dados em comentários são processados.