Unverified50% confidenceTradeoffExact time
Setting {"thinking": {"type": "disabled"}} can turn off thinking mode to avoid the 400 error, but it forgoes the model's reasoning capability and is not recommended as a regular workaround.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedClaude Opus 5.5 cannot disable thinking: at all effort levels it rejects thinking.type set to disabled, as well as the combination of enabled + budget_tokens, and the API returns a 400 error.71% similarUnverifiedSome official documentation warns that thinking mode should avoid greedy decoding to prevent performance degradation or falling into repetitive loops.67% similarUnverifiedException handling should be added to tool logic—for example, in a division branch, an error should be raised when the divisor is 0 rather than letting the program crash.65% similarUnverifiedAfter upgrading to 2.0.49, if the previous application logic relied on reasoning not being carried over, it may be necessary to explicitly disable that behavior.65% similarUnverifiedA 'Thunder Deep Think' anomaly occurred: after the chain of thought completed, the model output 'stop' and halted without entering the main text generation phase; the author mitigated this by patching in detection of 'stop' followed by a forced jump to the main text branch.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067660API
curl https://kongchang.com/api/v1/knowledge/claims/1067660MCP
get_claim(id=1067660)