Gemini 3.6 Flash (gemini-3.6-flash) and Gemini 3.5 Flash-Lite (gemini-3.5-flash-lite) are generally available (GA) and ready for production use.
This guide explains what's new in each model, what API changes affect your code, and how to migrate.
Both models support the 1M token context window, 64k max output tokens, thinking, and the full suite of built-in tools including Computer Use.
For complete specs, see the model pages:
For detailed pricing, see the pricing page.
Use this table to select the right model and migration path for your workloads.
Both models require removing deprecated sampling parameters (temperature, top_p, top_k) and prefilled model turns. See API changes for details.
Due to its improved performance, Gemini 3.6 Flash is now the new default model powering the Antigravity agent in Gemini Managed Agents. This can be changed by setting a new field on the API.
Starting with Gemini 3.6 Flash and Gemini 3.5 Flash-Lite, the following API changes apply to these models and all future Gemini model releases.
Below are detailed explanations and code samples for each API change.
temperature, top_p, and top_k are deprecated and ignored. In future model generations, supplying these parameters returns an HTTP 400 error. Remove these parameters from all requests.
To improve determinism, define a system instruction with explicit rules for your specific use case.
API requests ending with a non-empty model role turn are disallowed and return an HTTP 400 Error.
In legacy generateContent or raw REST payloads, ending with a model role turn is now disallowed:
In the Interactions API, model turns are not manually prefilled. If your application previously prefilled a model turn to suppress preambles or force JSON formatting, use system_instruction or Structured outputs instead.
Source: Hacker News — This article was automatically imported from the source. Read full article at original source →
