Something can no longer be bought new starting today. On October 9, Google ended new Gemini Code Assist Standard and Enterprise subscription sales. Existing contracts keep working and stay supported until their term ends. Start with the distinction that prevents most confusion: this is not the end of Gemini models or the Gemini API. It is the end of a code-completion product SKU, plus migration guidance toward an agent-based development platform.

The schedule: not a single switch-off

The shutdown arrives as stairs. Remember three dates:

2026-10-09  No new Standard/Enterprise subscriptions
            → existing subs work and stay supported to term end

2027-01-31  No license-count increases, no annual renewals

2027-12-31  No monthly renewals
            → contractual run-off only after that

Two preludes came first. On June 18, 2026, consumer IDE extensions and Gemini CLI serving (Individuals, AI Pro, Ultra) were cut, with Standard and Enterprise explicitly unaffected. On September 4, console self-serve purchases on billing accounts without an active Code Assist sub were blocked, and on September 17, newly bought or renewed Gemini Enterprise online stopped including Code Assist features. The successor has had the same name throughout: Antigravity with AI developer tools.

Official docs live in three places: the sunset page, the feature deprecations table, and the October 9 Code Assist release notes. If you bookmark them for the team wiki, save in that order. When dates move, the table moves first.

What ends vs what stays

The most misunderstood part, as a table:

Ending (Code Assist Standard/Enterprise SKUs):
  - new purchases after Oct 9
  - license increases + annual renewals after Jan 31, 2027
  - monthly renewals after Dec 31, 2027
  - console self-serve for net-new billing accounts (blocked since Sept 4)

NOT ending:
  - existing Standard/Enterprise entitlements → work to contract end
  - Gemini models, Vertex AI, Gemini Enterprise app, Agent Platform
  - sibling products like Cloud Assist
  - IDE extensions, Gemini CLI, GitHub integration until contract end

Do not mix June's consumer cutoff with October's enterprise end-of-sale. Consumer tiers lost Login with Google access itself; enterprise "will no longer be sold." Paid seats run to term end.

Migration paths: Plan A and Plan B

Google's direction is one sentence. Agentic coding assistance going forward lives in Antigravity, included in Gemini Enterprise editions.

Plan A — Gemini Enterprise license (for governed teams)
  Standard / Plus / pay-as-you-go + invoiced billing account
  → enable per location in Gemini Enterprise > Settings > AI developer tools
  → Antigravity 2.0, Antigravity CLI (agy), Antigravity for IDEs,
     Android Studio canary, pooled quotas, overages, spend caps,
     admin security and model controls, audit logging

Plan B — Agent Platform API (consumption, good for pilots/automation)
  → connect straight to aiplatform.googleapis.com with consumption billing
  → same clients without seats

One exception: if you truly need more of the Code Assist SKU, confirm in writing with sales or your account team before your final renewal. September notes mention a "contact sales" path, but after October 9 treat new Standard/Enterprise SKUs as closed unless a rep confirms otherwise.

If client names confuse you, memorize this: standalone Antigravity IDE is not supported for enterprise. Enterprises go with Antigravity 2.0, the agy CLI, and IDE extensions (Google.google-antigravity on the VS Code Marketplace, the Visual Studio 2026 VSIX, JetBrains/Zed/Xcode previews).

What changes in IDEs, CLIs, and auth

Nothing breaks tomorrow. But the migration punch list is long. Read it as a preview:

Auth: Sign in with Gemini Enterprise (Google Cloud SSO)
      or BYOID/WIF, headless ADC
      (gcloud auth application-default login, AGY_ADC_AUTH=true)
  → different from personal Login with Google
  → license picker selects Project + global/us/eu

IAM: users need roles/discoveryengine.agentspaceUser (+ license)
     admins need agentspaceAdmin (admin role alone cannot use)

Enable first: discoveryengine + businessaicode (+ aiplatform for Plan B)
  → license purchases can fail to provision without them

Network: allow businessaicode + discoveryengine families on 443,
         check VPC-SC, data residency, Model Armor, sandbox/MCP policy
  → third-party Claude (Opus/Sonnet 5.5) only in global/us/eu

CLI move (Gemini CLI → agy):
  agy plugin import gemini
  .gemini/skills/ → .agents/skills/
  MCP from ~/.gemini/settings.json → mcp_config.json
  url/httpUrl → renamed serverUrl
  GEMINI.md / AGENTS.md context files carry over

The rule from the using multiple AI tools post applies here too. Sort by task type and by auth and billing owner before tool names. Moving from personal accounts to enterprise SSO, project, and location scoping is the essence of this migration.

Ten things to check today

The briefing's action item, expanded into a checklist in order:

1. SKU + billing account: which account holds the Code Assist sub?
2. Cycle: annual vs monthly, exact term end, auto-renew flag
3. Seat headroom: clean up additions and inactive seats before the Jan 31, 2027 freeze
4. Contract: confirm SLA and model-update coverage for run-off with reseller/account team
5. Pick Plan A/B + invoiced billing + enable the three APIs
6. IAM + WIF/BYOID + project/location strategy (licenses are per project+location)
7. Firewall, proxy, VPC-SC + regional endpoint (global/us/eu)
8. Extension pilot: validate google-antigravity alongside Code Assist
9. Port skills, MCP, themes + verify /plan, /boost, agent mode, private-repo indexing parity
10. FinOps: pooled quotas, overages, spend caps, Claude opt-in billing, usage dashboards

The last half of item 9 is the trap. Private-repo code customization has no stated Antigravity equivalent in the docs. If you rely on it, get written confirmation from Google. Same for the GitHub code-review enterprise version.

Conclusion: the autocomplete-era SKU is closed

One line to summarize.

What became unbuyable is not models but the "autocomplete subscription" way of selling.

AI coding tools are reorganizing from code-completion products into agent-based IDEs and development platforms. The urgent job is not migration but inventory. Write down today's IDE extensions, CLI, auth method, team licenses, and contract end dates. Only that table tells you Plan A vs Plan B and how long you can still add seats. Teams that ran the vibe-coding web development flow from plan to deploy on Gemini CLI will get the feel of the agy move much faster.

Further reading

References

Go deeper with a course

If you have connected planning, implementation, and deployment with Gemini CLI and MCP, the agy and Antigravity-for-IDE move reads with the same intuition. To learn agent-style development flows hands-on first, start here.