How to Set Thinking Levels in Gemini 4 Argon
Step-by-step guide to using low, medium, and high thinking levels in Gemini 4 Argon for better quality, speed, and cost control.
Gemini 4 Argon gives developers direct control over how deeply the model reasons before it answers. The thinking_level parameter lets you trade latency and token cost for higher quality on hard problems.
Google released Argon on October 13, 2026, with support for three levels: low, medium (the default), and high. Medium balances speed and accuracy for most coding and agent work. High unlocks stronger results on multi-step debugging, formal reasoning, and long-horizon tasks.
This guide shows how to set the level in the Gemini API, when to choose each option, and how to measure the difference.
Why thinking levels matter
Earlier Gemini models used a thinking budget that counted tokens. Argon replaces that with named levels. You cannot turn thinking off. The model always reasons, but the depth changes.
Low uses the fewest tokens and returns the first answer fastest. Medium is the recommended starting point. High spends more tokens on internal reasoning and produces better first-pass results on difficult prompts.
Run the same prompt at all three levels during evaluation. Pick the lowest level that meets your quality bar. That approach keeps costs predictable while preserving performance where it counts.
For Android integration details, see our earlier guide on adding Gemini 4 Argon to Android with Firebase AI Logic.
Set the level in the Interactions API
Install the latest Google Gen AI SDK. Argon requires google-genai version 2.30.1 or higher for Python.
pip install -U "google-genai>=2.30.1"
Create a client and pass thinking_level inside generation_config:
from google import genai
client = genai.Client()
interaction = client.interactions.create(
model="gemini-4-argon",
input="Design a lock-free ring buffer in Rust for multi-producer telemetry.",
generation_config={
"thinking_level": "high" # or "low" or "medium"
}
)
print(interaction.output_text)
The same pattern works in the GenerateContent API. Use ThinkingConfig with thinking_level set to LOW, MEDIUM, or HIGH. Setting thinking_budget or MINIMAL returns a validation error.
Default is medium. Omit the field if that matches your needs.
Choose the right level
| Level | Best for | Trade-off |
|---|---|---|
| low | Classification, extraction, simple routing | Fastest, lowest cost, may miss edge cases |
| medium | Most coding, tool use, document Q&A | Balanced quality and speed |
| high | Multi-file debugging, formal proofs, architecture | Highest quality, higher latency and token use |
Start every new prompt at medium. Raise to high only after you confirm medium fails your evaluation criteria. Drop to low for high-volume classification pipelines where a small accuracy drop is acceptable.
Argon supports a unified 1 million token context that covers both input and output. Long decode continuation works best with high thinking levels on complex generation tasks.
Measure impact
Log the thinking tokens and total output tokens for each level. High typically consumes more thinking tokens before the first visible token arrives.
Run a small eval set of 20–50 representative prompts. Score correctness, completeness, and latency. Many teams find medium sufficient for interactive coding while high improves success rate on agentic multi-step jobs.
Introductory pricing through November 30, 2026 is $2 per million input tokens and $10 per million output tokens. Cached input tokens receive a 95 percent discount. After that date the rates become $4 and $20.
Monitor usage in Google AI Studio or your Cloud billing dashboard. Set budget alerts so unexpected high-level usage does not surprise you.
Tips for production
Keep the thinking level in configuration, not hard-coded. That lets you switch levels per endpoint or per user tier without a code change.
For background or long-running jobs, pair high thinking with the background execution flag and a higher max_output_tokens. Argon can continue past the single-request limit using continuation tokens.
Test safety ratings on both medium and high. Higher reasoning can surface more edge-case refusals or more detailed explanations.
If you previously used a thinking budget with earlier models, migrate the value to the closest named level and re-test. The semantics differ.
Conclusion
Thinking levels give you precise control over Gemini 4 Argon’s reasoning depth. Medium is the safe default for most work. High improves results on hard coding and agent tasks at higher cost. Low keeps high-volume pipelines fast and inexpensive.
Set the level in generation_config, measure on your own prompts, and adjust. The model is available today on the paid Gemini API tier and in Google AI Studio for Ultra subscribers.
Sources
- Gemini API docs: What’s new in Gemini 4 Argon (Interactions API)
- Google AI Studio: Gemini 4 Argon Developer Guide
- Official pricing page for Gemini models
Share this story