Google’s Gemini 3.6 Flash and Gemini 3.5 Flash-Lite are already generally available in the Gemini API, AI Studio, Gemini app, Gemini Enterprise, and Google’s agent tooling—but Gemini 3.5 Flash Cyber is not a product most developers or security teams can simply select. The practical split behind Google’s three-model announcement is sharper than the headline suggests: two public production models aimed at lowering the cost of agent workloads, and one restricted cyber model available only through the CodeMender program to governments and trusted partners.

Cloud Wars published its account on August 7, but Google’s launch record dates the three-model announcement to July 21, 2026. The supplied story also characterizes Gemini 3.6 Flash as replacing Gemini 3.5 Flash. Google is clearly positioning 3.6 Flash as the preferred newer workhorse, yet its current deprecation register does not list a retirement date or recommended replacement for the

gemini-3.5-flash

endpoint. Existing API deployments are not being forcibly migrated today.

That distinction is more than release-note pedantry. Companies with production prompt evaluations, tool schemas, safety checks, and spend controls should treat 3.6 Flash as an elective upgrade that needs validation, rather than assume an automatic model swap is underway.

Futuristic AI dashboard comparing Gemini models for efficiency, throughput, and cybersecurity.Gemini 3.6 Flash lowers the rate card and targets verbosity​

Gemini 3.6 Flash, model ID

gemini-3.6-flash

, takes over the high-throughput general-purpose role from Gemini 3.5 Flash. It accepts text, images, video, audio, and PDFs, supports a 1,048,576-token input context and up to 65,536 output tokens, and returns text rather than generated images, audio, or video.

Google’s core claim is that the new Flash model consumes 17% fewer output tokens than 3.5 Flash on the Artificial Analysis Index, while also requiring fewer reasoning steps and tool calls in some multistep workflows. Google says that translates into better coding, knowledge-work, and multimodal performance at lower cost; TechCrunch and Ars Technica both reported the launch and the absent Gemini 3.5 Pro release.

The hard-dollar comparison is clearer than the vendor language. Gemini 3.6 Flash is priced at $1.50 per million input tokens and $7.50 per million output tokens. Gemini 3.5 Flash remains listed at $1.50 input and $9 output. Input pricing is unchanged; output is roughly 16.7% cheaper before any token-efficiency benefit is counted.

For workloads dominated by generated text and reasoning tokens, the two changes compound. If a task truly uses 17% fewer output tokens and those tokens cost $7.50 rather than $9 per million, the output portion of that task costs roughly 31% less. That is a meaningful reduction for an agent that repeatedly drafts code changes, summarizes logs, produces test plans, or prepares support responses.

It is not, however, a universal 31% saving. Large Windows deployment inventories, event-log corpora, ticket exports, and document-analysis jobs can be input-heavy. Search grounding also carries its own metered charge after Google’s shared monthly allowance. The operational test is therefore not Google’s token benchmark but a replay of an organization’s own prompts, tool calls, and source documents.

Google’s API documentation calls out a second issue that tends to get lost in the performance charts: the sampling controls

temperature

,

top_p

, and

top_k

are deprecated. Teams that have used those parameters to stabilize PowerShell generation, incident-response summaries, or structured automation should test API behavior during migration, not merely switch the model name.


Flash-Lite is cheaper to run than Flash, but it costs more than its predecessor​

Gemini 3.5 Flash-Lite, model ID

gemini-3.5-flash-lite

, is Google’s volume tier. The company rates it at 350 output tokens per second through the Artificial Analysis measurement and positions it for high-throughput work such as classification, translation, document processing, retrieval subagents, and repetitive customer-service tasks.

At $0.30 per million input tokens and $2.50 per million output tokens, it is vastly cheaper than Gemini 3.6 Flash’s standard API pricing. For organizations using a controller-and-worker agent design, the sensible pattern is increasingly obvious: use 3.6 Flash for planning and harder reasoning, then delegate extraction, tagging, routing, first-pass summaries, and other routine steps to Flash-Lite.

But “most cost-effective” needs context. The prior Gemini 3.1 Flash-Lite rate was $0.25 per million text, image, and video input tokens and $1.50 per million output tokens. Gemini 3.5 Flash-Lite’s input price is 20% higher and its output price is about 67% higher. Google’s argument is that the new model is materially stronger and can complete agentic tasks with fewer calls or less reasoning; it has published benchmark gains in coding, long-context work, and computer use to support that claim.

The bill does not automatically fall just because a model has a Lite label. A Windows administrator using it to classify thousands of Intune remediation logs may save on latency and avoid escalating work to a larger model. A developer using it to generate lengthy reports, verbose code explanations, or repeated agent traces can still spend more per output token than on 3.1 Flash-Lite. The right comparison is completed-work cost and error rate, not the front-page price.

Flash-Lite has the same million-token input context and 65,536-token output ceiling as 3.6 Flash, and it supports tools such as function calling, search grounding, and computer use. That means Google is selling it as more than a basic chatbot model. It is a candidate for the high-fan-out workers in an automated system, where a more expensive model would be called hundreds or thousands of times.

The Cyber model is a controlled CodeMender capability, not an API release​

Gemini 3.5 Flash Cyber is the most consequential announcement and the least available one. Google DeepMind describes it as a lightweight model built on Gemini 3.5 Flash and fine-tuned to find, validate, and patch software vulnerabilities. The company says it will be used through CodeMender, its code-security agent, in a limited-access pilot for governments and trusted partners, with broader expansion promised but no public timetable.

That makes the Cloud Wars framing of a new model launch technically correct but potentially misleading for IT buyers. There is no public Gemini API model ID to plug into an application, no published public price, no general-access enrollment path, and no stated date when ordinary enterprises can use the specialized model. TechRepublic similarly reported that the best-equipped version of CodeMender remains restricted while the general offering is in preview.

Google has published striking internal and benchmark claims. It says a CodeMender configuration that invokes Flash Cyber up to five times can compete with much larger models on CyberGym, and that the model found 55 confirmed unique issues in an evaluation of V8, compared with 47 for mainline Gemini 3.5 Flash and 36 for Claude Opus 4.6. Google also says the model has been finding and fixing vulnerabilities across internal codebases including Chrome, Android, Cloud, Ads, and YouTube.

Those are Google’s results, not independently replicated field evidence. The five-call detail is especially important: the demonstrated capability belongs to the CodeMender orchestration system, repeated model invocations, tooling, and verification loop—not necessarily to one prompt sent to a model. Security teams should resist treating a vulnerability-finding benchmark as proof that an agent can be allowed to author and deploy production patches without review.

Google’s restricted rollout also reflects the dual-use problem. A model capable of recognizing a flaw, determining whether it is exploitable, and generating a reliable proof of concept can help defenders close holes faster, but the same sequence can shorten an attacker’s path from source access to exploitation. Limited access reduces that exposure, but it also means the announcement changes little for a Windows-centric enterprise that wants to scan a private .NET, C++, PowerShell, or driver codebase this quarter.


Gemini 3.5 Pro remains the missing product​

Google acknowledged that Gemini 3.5 Pro is still being tested with partners and said it plans broad availability once it is ready. It did not announce a release date, technical specification, price, or API model ID. Axios noted that Bloomberg had reported the anticipated flagship was months behind schedule, but Google’s own announcement offers no timetable beyond the open-ended partner-testing statement.

The absence matters because 3.6 Flash is being asked to cover two jobs: be a low-latency, lower-cost operational model and provide enough reasoning quality for increasingly complex agent workflows. Google’s product line now has an efficient public workhorse, a high-volume worker tier, and a gated security specialist. It still lacks a newly released public flagship in the 3.5 generation.

For now, the immediate action is straightforward. Test

gemini-3.6-flash

against existing

gemini-3.5-flash

evaluations before moving a production workflow, route truly repetitive subagent work to

gemini-3.5-flash-lite

, and do not budget around Flash Cyber unless Google has explicitly admitted your organization to CodeMender. The older 3.5 Flash endpoint remains live with no announced shutdown date, while the cyber capability remains a promise of access rather than a tool most defenders can deploy.


References​

  1. Primary source: Cloud Wars
    Published: August 7, 2026 at 3:00 PM UTC
  2. Related coverage: deepmind.google
  3. Related coverage: deepmind.google
  4. Related coverage: ai.google.dev
  5. Related coverage: blog.google
  6. Related coverage: ai.google.dev
  7. Related coverage: techcrunch.com
  8. Related coverage: blog.google
  9. Related coverage: apidog.com
  10. Related coverage: techrepublic.com
  11. Related coverage: techradar.com
  12. Related coverage: cincodias.elpais.com
  13. Related coverage: tokencost.app
  14. Related coverage: github.blog
  15. Related coverage: aicost.tools
  16. Related coverage: aireiter.com
  17. Related coverage: axios.com
  18. Related coverage: discuss.ai.google.dev
  19. Related coverage: concentrate.ai
  20. Related coverage: storage.googleapis.com
  21. Related coverage: modelcards.withgoogle.com
  22. Related coverage: androidcentral.com
  23. Related coverage: tomsguide.com
  24. Related coverage: techradar.com
  25. Related coverage: reposhub.com
  26. Related coverage: 9to5google.com
  27. Related coverage: artdirectiondaily.com
  28. Related coverage: apidog.com
  29. Related coverage: codingsalt.com
  30. Related coverage: arstechnica.com
  31. Related coverage: agentpedia.codes
  32. Related coverage: storage.googleapis.com
  33. Related coverage: androidcentral.com