Repository navigation
fix(gemini): send the lowest thinking level when thinking is 'none' on Gemini 3 - #9278
Conversation
There was a problem hiding this comment.
All reported issues were addressed across 3 files
Heads up: you’re close to your flex budget. Increase your flex budget so reviews don’t pause.
Turn on auto-fix | Re-trigger cubic
[Medium impact] The PR appears safe to merge; no actionable issues were found. SummaryGemini 3 requests with
Reviews (3) · Last reviewed commit: "fix(gemini): resolve the lowest thinking..." · Reviewed by Greptile |
|
@greptile |
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 4 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’re close to your flex budget. Increase your flex budget so reviews don’t pause.
Turn on auto-fix | Re-trigger cubic

Summary
noneon Gemini 3 models sent nothinkingConfig, so the API fell back to the model's default level (medium/high) and kept thinkingnonenow sends the lowest level the model declares:minimalwhere offered (closest to off per Google's docs),lowon models that rejectminimal(3.7/3.8-flash, 3.1/3-pro)noneModeTSDoc to reflect the Gemini 3 ruleType of Change
Testing
providers/gemini/core.test.ts(3.6-flash → MINIMAL, 3.8-flash → LOW); failed before the fix, passes aftervitest run providers/— 177 files, 2103 tests passing; biome cleanexecuteGeminiRequestwithnone(output tokens incl. thoughts, before → after): 3.6-flash 418 → 20, 3.8-flash 277 → 21, 3.7-flash 325 → 20, 3.5-flash 518 → 89; 3.1-pro-preview still thinks (it only runs in thinking mode)MINIMALis rejected on 3.7/3.8-flash and 3.1-pro;thinkingBudget: 0is rejected on 3.5-flash-lite and 3.1-pro, so it isn't a safe general off switchChecklist
test-auditauthoring gate)