Gemini Code Assist Sales End: Renewal Deadlines and Antigravity Migration

Google ended new Gemini Code Assist Standard and Enterprise subscription sales on October 9, 2026, according to its dated release notes. Engineering leaders and procurement owners evaluating those paid coding tools now need a replacement purchasing route; current customers need a transition schedule.

Google points teams toward Antigravity through eligible Gemini Enterprise subscriptions or Gemini Enterprise Agent Platform. The announcement identifies both routes. Existing Code Assist subscriptions remain usable and supported for their contractual term, under Google’s sunset policy.

Start with your contract dates and headcount plan, then evaluate the replacement’s eligibility, costs and workflow compatibility.

Separate license growth from renewal deadlines

Google’s published transition schedule sets different limits for expansion and renewal:

These are action cutoffs, not a single shutdown date. Confirm the final eligible renewal and resulting contract end for your agreement. The notice does not promise automatic migration, refunds or a switch in billing cadence to extend access.

Planning implication: a monthly customer may still be renewing after it can no longer add licenses. If you expect hiring or wider adoption after January 2027, plan replacement capacity independently of the legacy contract’s remaining life.

Choose the purchasing route before buying more tools

Do not confuse Gemini Code Assist Enterprise, the retiring coding subscription, with Gemini Enterprise, the broader replacement bundle. The Gemini Enterprise edition matrix includes AI developer tools in Standard, Plus and Pay-as-you-go, but not Business or Frontline.

Antigravity’s organizational pricing page lists the following options. The decision column is a planning framework, not a tested cost ranking.

The starting price is not a Plus-specific quote or a migration discount. Obtain terms for your account and compare total usage costs. For the wider workplace decision, see our Gemini Enterprise pilot guide.

For the subscription route, Google requires an invoiced Cloud Billing account, an eligible subscription and the appropriate usage role. The Admin role alone does not grant developer-tool access. Check project, location and license assignment against the setup prerequisites. Direct API access follows a separate onboarding path.

Budget for busy weeks, not just a monthly seat price

Google lists developer-tool credits of US$10 per Standard user per month and US$15 per Plus user per month. It enforces these as seven-day pools, separated by edition, project and location. Unused quota does not carry forward. See the quota rules.

Calculated example: assuming 20 licensed seats of one edition in one project and location, Standard provides 20 × US$10 ÷ 4 = US$50 per seven-day pool; Plus provides 20 × US$15 ÷ 4 = US$75. This applies Google’s documented formula, not observed usage. It does not estimate how many coding tasks those credits buy.

If overages are off, reaching the pooled quota stops feature usage. If they are on, set a spending limit and account for other services sharing the project budget. Google warns that stopping chargeable usage can take minutes, allowing the cap to be exceeded. The overage controls therefore need both a budget owner and a decision about acceptable interruptions.

Keep the editor if appropriate, but check enterprise support

Antigravity’s IDE extensions provide an existing-editor option for VS Code, Visual Studio, JetBrains, Zed and Xcode. That can reduce the scope of a migration: changing the coding assistant need not mean changing the editor.

However, the enterprise support matrix distinguishes Antigravity 2.0, CLI and IDE extensions from the standalone Antigravity IDE. The standalone IDE is not currently supported for enterprise deployments. JetBrains, Zed and Xcode enterprise integrations are marked Preview. Treat the exact client and release status as acceptance criteria, not just the Antigravity brand name.

For Gemini CLI users, migrate configuration deliberately

The CLI migration guide documents first-launch asset selection and this manual command for importing Gemini CLI extensions as Antigravity plugins:

agy plugin import gemini

The command is documented here, not executed or tested for this article. Back up the existing configuration and review the selected assets and import output. Google identifies several compatibility details:

• Context documents: GEMINI.md and AGENTS.md remain supported.

• Skills: global skills move from ~/.gemini/skills/ to ~/.gemini/antigravity-cli/skills/; project skills move from .gemini/skills/ to .agents/skills/.

• MCP servers: definitions move out of ~/.gemini/settings.json into ~/.gemini/config/mcp_config.json or .agents/mcp_config.json. Remote definitions use serverUrl instead of url or httpUrl.

• Terminal customization: some themes and experimental visual overlays may not be supported.

A completed import is not evidence that scripts, headless jobs, hooks or connected tools still behave correctly. Build the acceptance check around the workflows your team actually depends on.

Approve the deployment, not just the login

For existing eligible subscriptions, an administrator must enable developer tools per location. The subscription setup requires the Discovery Engine and Business AI Code APIs, alongside licensing and IAM. Google’s settings documentation lists terminal auto-execution as “Always proceed” and sandbox mode as disabled by default. Review the actual tenant settings before a pilot.

Third-party models require administrator opt-in and enabled overages. Their usage is billed separately from pooled Gemini credits, and background Gemini coordination can also incur charges. These are documented billing rules, not evidence of a particular team’s bill.

For regulated deployments, check the product-specific compliance limitations: Google lists exclusions including FedRAMP, ISO certifications, SOC 1/2/3 and Access Transparency for Antigravity in Gemini Enterprise. This is not a statement about Google Cloud as a whole. An existing vendor approval does not establish that this particular tool meets your requirements.

Before committing to a cutover, require three concrete outputs:

• A procurement record with the current agreement’s end date, final renewal, seat-expansion needs and replacement quote.

• A deployment record identifying the supported client, edition or API route, project/location, access roles, execution settings and budget behavior.

• A separate pilot record for representative coding and automation tasks: repository revision, prompts, client/model versions, permissions, outputs and costs. Record unsupported integrations and a fallback before wider rollout.

If a required client, certification or workflow fails those checks, evaluate another supported deployment or replacement while the existing agreement still provides continuity.

Methodology: AI-assisted reporting and analysis based on Google’s published documentation, rechecked on October 9, 2026. No hands-on migration, performance benchmark or customer outcome is claimed.