Version 5

Google released Gemini 3.6 Flash and 3.5 Flash-Lite on July 21, 2026, replacing 3.5 Flash just two months after its Google I/O debut, while Gemini 3.5 Pro remains unreleased due to coding performance shortfalls compounded by organizational problems including clashing teams and frustrated engineers [1][10][8]. Google also released Gemini 3.5 Flash Cyber, a security-specialized variant restricted to governments and trusted partners, which in internal tests found more vulnerabilities in Chrome's V8 engine than Claude Opus 4.6 [4]. Google has disclosed it has begun pre-training Gemini 4, calling it its most ambitious effort yet, with no timeline attached [1][15].

The Gemini 3.5 Pro delay has both technical and organizational dimensions — benchmark shortfalls and internal team friction — making its resolution timeline harder to read than a simple performance gap. Flash Cyber's restricted-access model may not hold as a competitive differentiator if a competitor ships equivalent capabilities without access controls.

Google released three Gemini models in quick succession in July 2026. Gemini 3.6 Flash, released July 21, replaces 3.5 Flash just two months after its Google I/O debut, claiming 17% fewer output tokens and improvements on benchmarks where 3.5 Flash had underperformed, including DeepSWE coding (49% vs. 37%) and OSWorld computer use (83.0% vs. 78.4%) [1]. Gemini 3.5 Flash-Lite, released the same day, targets high-volume latency-sensitive workloads at 350 output tokens per second and is being integrated into Google Search [1][2]. 3.6 Flash is priced at $1.50 per million input tokens and $7.50 per million output tokens [2]. Ars Technica argued that Google's efficiency-first training priorities may have produced the coding underperformance in 3.5 Flash that 3.6 Flash corrects, and noted the awkward optics of deprecating a two-month-old flagship [3].

Four days before the Flash releases, Google announced Gemini 3.5 Flash Cyber, trained specifically for offensive and defensive security work. In internal evaluations it found 55 unique confirmed vulnerabilities in Chrome's V8 JavaScript engine versus 47 by mainline 3.5 Flash and 36 by Claude Opus 4.6 [4]. In a two-hour test on Google's own production systems, it uncovered remote code execution vulnerabilities in public APIs and a memory-corruption flaw in a sensitive service, then generated a functional RCE exploit bypassing both ASLR and W^X mitigations [4]. Google restricted the model to governments and trusted partners via its CodeMender platform. The Verge and CyberNews framed Flash Cyber primarily as a cheaper alternative to large dedicated AI security models such as Mythos [5][6]. A YouTube comparison positioned Flash Cyber as outperforming both Claude Mythos and GPT 5.6 Sol on cybersecurity tasks [7], though without new benchmark methodology. The Neuron argued that the gatekeeping logic holds only as long as no competitor ships an equivalent model without restrictions [2].

The unresolved delay of Gemini 3.5 Pro has an organizational as well as a technical dimension. Bloomberg first reported in mid-July that the model had been held back because coding performance fell short of internal targets [8], and Alphabet's share price fell on that report [9]. The LA Times subsequently published an account drawing on internal sources describing coding stumbles alongside clashing teams and frustrated engineers — adding an organizational layer to what Google had characterized as a pure performance problem [10]. Secondary outlets including Firstpost and Neowin amplified the delay story without adding new claims [11][12]. InfoWorld argued the CEO's decision to emphasize Gemini 4 pre-training and a monthly release cadence served to redirect public attention from the stalled Pro model [13].

Google has disclosed that Gemini 4 pre-training has begun, describing it as its most ambitious pre-training effort yet, without attaching a timeline or capability claims [1][14][15]. The announcement drew broad secondary amplification across social media and smaller tech outlets [16][17] but produced no new factual claims beyond what Google originally stated. Some commentary connected the Gemini 4 announcement to possible disappointment with 3.5 Pro development [15], a link Google has not confirmed.