Enterprise Gemini CLI users were promised access to the latest models — so where are Gemini 3.5 Flash and 3.6 Flash?

During the Gemini CLI migration announcement on May 19, 2026, Google explicitly stated:

> “If your organization uses Gemini CLI or our IDE extensions via a Gemini Code Assist Standard or Enterprise license, your access remains unchanged. We’ll continue to support Gemini CLI and Gemini Code Assist with access to the latest Gemini models and other updates.”

I relied on this statement when continuing to purchase and maintain Gemini Code Assist Enterprise credentials.

However, the actual situation does not match that promise.

Gemini 3.5 Flash became generally available on May 19, 2026. It has now been available for 76 days, yet my Enterprise-authenticated Gemini CLI still cannot reliably access or select it.

Gemini 3.6 Flash was released on July 21, 2026. Google Antigravity received access to it immediately on release day, while Gemini CLI enterprise users are still left without access. In my current Gemini CLI environment, the newest model I can actually use is still from the Gemini 3.1 generation.

This raises a very simple question:

**What exactly does “access to the latest Gemini models” mean?**

Does it mean access on release day?

Does it mean access several weeks or months later?

Or does it simply mean that Gemini CLI might receive newer models at some unspecified point in the future?

This is not an isolated complaint. There are already multiple reports in this repository involving Gemini 3.5 Flash access and model-selection failures, including:

* #27258 — `gemini-3.5-flash` not working in Gemini CLI
* #27688 — Gemini 3.5 Flash unavailable through Vertex AI after upgrading Gemini CLI
* #27789 — Gemini 3.5 Flash defined in the CLI configuration but unavailable for selection or use

The repository configuration already contains routing and feature flags for Gemini 3.5 Flash, yet access remains inconsistent or completely unavailable depending on the authentication method, license, CLI version, or an undocumented server-side rollout condition.

At the same time, newer models are made available immediately in Antigravity.

From an enterprise customer’s perspective, this creates the impression that Gemini CLI has effectively entered maintenance mode, while Google continues to describe it as a supported enterprise product that receives the latest models.

Please provide clear answers to the following questions:

1. Is Gemini CLI still under active model development for Gemini Code Assist Standard and Enterprise customers?
2. When will Gemini 3.5 Flash and Gemini 3.6 Flash be fully available through Enterprise authentication?
3. Which authentication methods are officially supported for each model: Gemini Code Assist OAuth, Gemini API keys, or Gemini Enterprise Agent Platform credentials?
4. Is there a documented model-release schedule or service-level target for Enterprise Gemini CLI users?
5. Will future Gemini models continue to be added to Gemini CLI, or will they only be made available through Antigravity CLI?
6. If Gemini CLI is now a maintenance-only or legacy product, why has this not been clearly announced?

Please do not respond with another vague statement such as “availability is being rolled out gradually.”

Enterprise customers need an explicit model-support matrix and a concrete roadmap. We need to know what we are actually purchasing and whether Gemini CLI remains a meaningful part of that purchase.

If Google has decided to stop keeping Gemini CLI current, please announce it directly.

That would allow me—and likely many other enterprise customers in the same situation—to make an informed decision about whether to renew or cancel our Gemini Code Assist Enterprise licenses.

The current situation is worse than a straightforward deprecation announcement: customers are being told that Gemini CLI will continue receiving the latest models, while the product remains multiple model generations behind Google’s preferred platform.

Please either honor the original commitment or clearly withdraw it.

Review the Gemini CLI configuration, routing, and feature flags mentioned in the issue, then compare related reports #27258, #27688, and #27789 across authentication methods. Done would require a confirmed model-support matrix and release commitment, or a clearly documented product-status response; the issue does not identify a specific code change or test.

Written by the indexing model from the issue text.