SaaS & Software·Jul 21, 2026

Gemini last models: temperature, top_p, and top_k are deprecated and ignored

This page 3.5 Flash 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. Gemini 3.6 Flash: Stronger performance on complex agentic and multimodal ta

Hacker News7 min readSingle source
Gemini last models: temperature, top_p, and top_k are deprecated and ignored
Image · Hacker News
The gist
5-point summary · 1 min

This page 3.5 Flash 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. Gemini 3.6 Flash: Stronger performance on complex agentic and multimodal ta

  • This page 3.5 Flash 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.
  • Gemini 3.5 Flash-Lite gemini-3.5-flash-lite minimal $0.30/1M input tokens and $2.50/1M output tokens The fastest, lowest-cost 3.5 model for high-throughput execution.
  • Both models support the 1M token context window, 64k max output tokens, thinking, and the full suite of built-in tools including Computer Use.
  • Enhanced reasoning and multimodal performance: Strong migration path from Gemini 2.5 Flash, with higher scores on reasoning tasks like HLE (18.0% vs.
  • Remove these parameters from all requests. # ⚠️ Remove these parameters (deprecated) generation_config = { "temperature": 0.7, "top_p": 0.9, "top_k": 40, } To improve determinism, define a system instruction with explicit rules for your specific use case.
$1.50$7.50$0.30$2.50$9.0018.0%
In this article

This page 3.5 Flash 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. Gemini 3.6 Flash: Stronger performance on complex agentic and multimodal tasks while reducing token usage, at a lower price point than 3.5 Flash. Gemini 3.5 Flash-Lite: The fastest, lowest-cost model in the 3.5 family. Outperforms prior Flash-Lite generations for high-throughput execution. This guide explains what's new in each model, what API changes affect your code, and how to migrate. Gemini 3.6 Flash Install the skill: npx skills add google-gemini/gemini-skills --skill gemini-interactions-api --global Apply the skill: /gemini-interactions-api migrate my app to Gemini 3.6 Flash Gemini 3.5 Flash-Lite Install the skill: npx skills add google-gemini/gemini-skills --skill gemini-interactions-api --global Apply the skill: /gemini-interactions-api migrate my app to Gemini 3.5 Flash-Lite New models Model Model ID Default thinking level Pricing Description Gemini 3.6 Flash gemini-3.6-flash medium $1.50/1M input tokens and $7.50/1M output tokens Balances speed with intelligence for agentic and multimodal tasks. Gemini 3.5 Flash-Lite gemini-3.5-flash-lite minimal $0.30/1M input tokens and $2.50/1M output tokens The fastest, lowest-cost 3.5 model for high-throughput execution. 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: Gemini 3.6 Flash model page Gemini 3.5 Flash-Lite model page For detailed pricing, see the pricing page. Quickstart Pythonfrom google import genai client = genai.Client() interaction = client.interactions.create( model="gemini-3.6-flash", input="Write a three.js script that renders an interactive 3D robot." ) print(interaction. ) JavaScriptimport { GoogleGenAI } from "@google/genai"; const ai = new GoogleGenAI({}); async function main() { const interaction = await ai.interactions.create({ model: "gemini-3.6-flash", input: "Write a three.js script that renders an interactive 3D robot.", }); console.log(interaction.outputText); } main(); RESTcurl "https://generativelanguage.googleapis.com/v1beta/interactions" \ -H "x-goog-api-key: $ " \ -H 'Content-Type: application/json' \ -X POST \ -d '{ "model": "gemini-3.6-flash", "input": { "parts": [{"text": "Write a three.js script that renders an interactive 3D robot."}] } }' What's new in Gemini 3.6 Flash Token and turn reduction: Completes multi-step workflows with fewer reasoning steps, conversational turns, and tool calls than Gemini 3.5. It also reduces execution loop spiraling. Improved code generation: Produces higher quality production-ready code with fewer unwanted edits and fewer debugging loops. Better instruction following: Reduces unwanted file changes during diagnostic tasks. Strong multimodal and spatial reasoning: Improved performance on chart interpretation, visual blueprint conversion, and multi-element web layout generation. Upfront programmatic inspection: Prefers running diagnostic code scripts before making changes more frequently than Gemini 3.5 Flash. This improves accuracy on complex tasks, but can add extra exploratory steps on simple frontend work. Computer Use support: Supported as native tool for agentic UI automation. UI styling preference: Better at creating functional code, though human evaluators preferred earlier models for visual layout and styling. You can mitigate this by providing explicit design guidelines. Default thinking effort (medium): Uses the same medium default thinking level as Gemini 3.5 Flash. Reduced pricing: Lower output token costs ($7.50/1M vs. $9.00/1M for 3.5 Flash). Input tokens remain at $1.50/1M. What's new in Gemini 3.5 Flash-Lite Reduced task execution latency: Highest throughput in the 3.5 family for high-volume data parsing and document extraction. Enhanced reasoning and multimodal performance: Strong migration path from Gemini 2.5 Flash, with higher scores on reasoning tasks like HLE (18.0% vs. 11.0%) and multimodal benchmarks like CharXIV (74.5% vs. 63.7%). Subagent orchestration and tool reliability: Improves tool execution reliability for code execution, search, and MCP workflows. Increase the thinking level for autonomous planning and complex subagent tasks. Improved document understanding: Improves accuracy on document parsing and structured data extraction. Experiment with both minimal and high thinking levels depending on document complexity. Interactive web coding and tabular data processing: Performs strongly on frontend JavaScript and tabular data processing by planning via lightweight code execution. Chatbot and persona persistence: Stronger multi-turn instruction following and persona consistency over Gemini 3.1 Flash-Lite. Computer Use support: Supported as native tool for agentic UI automation. Choosing the right Flash or Flash-Lite model 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. Model Primary use cases Recommended migration target Gemini 3.6 Flashgemini-3.6-flash Code generation, spatial/multimodal reasoning, multi-step agentic workflows Gemini 3.5 Flash, Gemini 3 Flash (Preview), or Gemini 3.1 Pro Gemini 3.5 Flash-Litegemini-3.5-flash-lite Autonomous subagent execution, high-volume data analysis and document extraction, structured JSON parsing Gemini 3.1 Flash-Lite or Gemini 2.5 Flash Updated Antigravity agent 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. Pythonfrom google import genai client = genai.Client() interaction = client.interactions.create( agent="antigravity-preview-05-2026", input="Read Hacker News, summarize the top 10 stories, and save the results as a PDF.", environment="remote", ) print(interaction. ) JavaScriptimport { GoogleGenAI } from "@google/genai"; const client = new GoogleGenAI({}); const interaction = await client.interactions.create({ agent: "antigravity-preview-05-2026", input: "Read Hacker News, summarize the top 10 stories, and save the results as a PDF.", environment: "remote", }, { timeout: 300000 }); console.log(interaction. ); RESTcurl -X POST "https://generativelanguage.googleapis.com/v1beta/interactions" \ -H "Content-Type: application/json" \ -H "x-goog-api-key: $ " \ -d '{ "agent": "antigravity-preview-05-2026", "input": "Read Hacker News, summarize the top 10 stories, and save the results as a PDF.", "environment": "remote" }' API changes and parameter updates 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. Sampling parameter deprecation: temperature, top_p, and top_k are deprecated. The API ignores these parameters and returns an error in future model generations. Prefilled model turn validation: Prefilling model turns is no longer supported. If the last non-empty turn in the request is a model turn, the API returns a 400 error. Below are detailed explanations and code samples for each API change. 1. Sampling parameter deprecation (temperature, top_p, top_k) 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. # ⚠️ Remove these parameters (deprecated) generation_config = { "temperature": 0.7, "top_p": 0.9, "top_k": 40, } To improve determinism, define a system instruction with explicit rules for your specific use case. 2. Prefilled model turn validation API requests ending with a non-empty model role turn are disallowed and return an HTTP 400 Error. ⚠️ Avoid In legacy generateContent or raw REST payloads, ending with a model role turn is now disallowed: /* ❌ DO NOT: End payload contents with a 'model' role turn */ { "contents": [ {"role": "user", "parts": [{"text": "Translate 'Hello world' to Spanish."}]}, {"role": "model", "parts": [{"text": "Translation:"}]} /* ❌ Returns error */ ] } ✅ Recommended Migration (Interactions API) 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 or Structured outputs instead. # ✅ RECOMMENDED: Use in the Interactions API to specify output format interaction = client.interactions.create( model="gemini-3.6-flash", input="Translate 'Hello world' to Spanish.", ="Output only the translation without introductory text.", ) Migration checklist Gemini 3.6 Flash Install the skill: npx skills add google-gemini/gemini-skills --skill gemini-interactions-api --global Apply the skill: /gemini-interactions-api migrate my app to Gemini 3.6 Flash Gemini 3.5 Flash-Lite Install the skill: npx skills add google-gemini/gemini-skills --skill gemini-interactions-api --global Apply the skill: /gemini-interactions-api migrate my app to Gemini 3.5 Flash-Lite Migrate to gemini-3.6-flash Update Model ID: Change your target model string to gemini-3.6-flash. Remove deprecated sampling parameters: Strip temperature, top_p, and top_k from generation configs. Replace with the string enum set to "medium" or "high". Remove candidate_count (unsupported in Gemini 3.x). Enforce turn validation rules: Standardize multi-turn conversations on server-side. Remove prefilled model turns. Audit function calling: Place multimodal assets inside the response payload. Format inline instructions using \n\n. If you see Malformed_Function_Call errors tied to pre-tool text, see Workarounds for pre-tool text requirements. Only if using generateContent API: Ensure all FunctionResponse objects include call_id and name. Baseline Gemini 3.x requirements: For SDK updates and thought signature preservation, see the Gemini 3.5 Migration Checklist. Migrate to gemini-3.5-flash-lite Update Model ID: Change your target model string to gemini-3.5-flash-lite. Configure thinking effort level: For high-volume extraction, routing, or classification: leave at "minimal" (default) for maximum throughput. For autonomous subagents with tool calls, code execution, or multi-step reasoning: set to "medium" or "high" to prevent premature tool termination. Remove deprecated parameters and validate function calling: Apply the same rules as 3.6 Flash. Baseline Gemini 3.x requirements: Refer to the Gemini 3.5 Migration Checklist. Next steps Review API specs on the Models Overview. Explore multi-agent orchestration in the Interactions API Guide. Test and refine prompts in Google AI Studio.

Integrity note  ·  Xela does not rewrite or paraphrase article content. The excerpt above is the source publication's own words, sanitized for display. For the full piece — including any quotes, charts, or images — read it at Hacker News. Xela's rewritten version is off for this story, so there's no editorial angle attached — you're getting the source's reporting unfiltered. When the rewrite is on, we add a What this means block underneath with the operator/trader takeaway.

What people are saying

Discussion

Hot takes

0/280

Loading takes…

Comments

Discussion · 0

Sign in to comment, like, and save articles.

Sign in

Loading comments…

Keep readingSaaS & Software desk
See all in SaaS
Show HN: Computable – Buy, sell, and redeem GPU for the exact weeks you want
·

Show HN: Computable – Buy, sell, and redeem GPU for the exact weeks you want

Hey we are Computable. We spent years building trading infrastructure at Jump Trading and Coinbase. From that point of view, compute looks like energy markets before 2000: everything trades through private bilateral leases, there’s no visible price, and nothing can be resold. The same H100 rents at a 2x spread depending on who’s asking, and once you sign a 24-month lease, it can never change hands. So we built a market for GPU nodes, sold by the calendar week. Here are three things you can do on it that you can’t do anywhere else: - Buy exactly the weeks you need. Three nodes for the last two weeks of October means you pay for those two weeks and walk away when the run is done. You don't have to commit to 6-24 months, and there's no flexibility premium. - Sell back what you don’t use. If your plans change, unused weeks turn back into cash: we keep a market quote posted on every position, so there’s always a price to hit. - Buy (or sell) the future. Lock January in July at a price you set, so the cost of a future run is known before another 40% H100 rate jump makes it not. The first auction is live now at : a block of nodes, August through the end of January. Bidding closes July 31. The bids are sealed. You bid how many nodes, which weeks, and your price. Every clearing price gets published after settlement, because nobody knows what a GPU week is worth and we want the prints to exist in public. Happy to go deep in the comments on anything, including the clearing mechanism, which is a packing problem and was fun to design! Comments URL: Points: 3 # Comments: 1

Hacker NewsSingle source
Newsletter

Track saas & software every morning.

Daily digest tuned to this beat. The 5 stories most worth your time. Unsubscribe anytime.