Google’s November 6, 2026 release notes set a concrete deadline for organizations receiving Gemini Code Assist through existing Gemini Enterprise Standard and Plus subscriptions. That bundled entitlement ends on March 31, 2027. The notice is a transition announcement, not an immediate shutdown.
Different subscriptions have different end conditions
Google’s sunset documentation distinguishes the bundled entitlement from a separate Gemini Code Assist subscription. Existing standalone subscriptions remain supported until their contractual end. Annual subscriptions can continue auto-renewing until January 31, 2027; monthly subscriptions have a December 31, 2027 renewal cutoff. Adding licenses is allowed until January 31, 2027.
New Code Assist Standard and Enterprise subscriptions stopped being available on October 9, and new Gemini Enterprise Standard and Plus subscriptions stopped including the entitlement then. The November notice clarifies the timetable for existing bundled access. Support is limited to the Gemini 3.x model family.
The named transition path is Antigravity
Google identifies Antigravity, included in Gemini Enterprise editions, as its route for agentic coding assistance. The documentation links IDE extensions and a CLI migration guide. That identifies a destination for evaluation; it does not establish that every team’s current setup transfers automatically.
Organizations should check the terms and supported features of the exact replacement they plan to use. Product names and shared subscription branding are insufficient evidence that administration, security controls, or everyday workflows are identical.
Make the migration inventory specific
Our operational analysis is to begin with how each developer actually receives access. Record whether it comes from the enterprise bundle or a standalone agreement, who owns billing, and which contract applies. That prevents a team from planning against the wrong date.
Then identify the working surfaces: IDE extensions, command-line tools, shared development images, and automated tasks. Include configuration that developers may have installed independently. A subscription change can become a workflow interruption when those dependencies are discovered only after access expires.
Test a representative assignment before switching
A useful pilot includes a normal repository change, the required checks, and the review process used by the team. Confirm sign-in, permissions, repository access, and where task output is stored. Have an administrator verify the controls that the organization depends on, rather than assuming a successful individual login proves readiness.
Keep a clear owner for the final transition and verify the intended licenses before removing older access. The important result is continuity of authorized work under a supported arrangement. Google’s dated notice provides time to make that transition deliberately, with subscription-specific evidence instead of a single deadline applied indiscriminately to every customer.