Skip to content
BENIBIX Learn

CLAUDE_CODE_DISABLE_THINKING vs MAX_THINKING_TOKENS=0

People think CLAUDE_CODE_DISABLE_THINKING turns thinking off. It does not. It only leaves the thinking field out of the request, for a proxy that rejects the field. A model that thinks by default may still think. MAX_THINKING_TOKENS=0 is the one that asks the Anthropic API for no thinking. On a cloud provider, both just leave the field out. Some new models cannot have thinking turned off at all.

AI⌨️ Claude Code

CLAUDE_CODE_DISABLE_THINKING

Set to 1, it leaves the thinking field out of each request.

CLAUDE_CODE_DISABLE_THINKING set to 1 leaves the thinking field out of each request. It is for a proxy that rejects that field. It does not turn thinking off. A model that thinks by default may still think. To ask for no thinking, set MAX_THINKING_TOKENS to 0.

Example
Emma's proxy failed every request with an error about thinking. She set this, and the requests went through.
Why it matters
Some proxies reject fields they do not know. This lets Claude Code work through them.
Full entry
AI⌨️ Claude Code

MAX_THINKING_TOKENS

It sets how many tokens Claude may spend thinking.

MAX_THINKING_TOKENS sets a fixed number of tokens Claude may spend thinking before it answers. It stays at least one token below the output limit, and never goes under 1,024. Models that pick their own depth ignore the number. Set to 0, it turns thinking off on the Anthropic API. The 5.5 models and Fable are the catch: their thinking cannot be turned off.

Example
Lucy runs an older model through a gateway and wants short, cheap answers. She sets a small thinking budget, and replies come back faster.
Why it matters
Thinking costs tokens and time. A fixed budget keeps both in check on models that use one.
Full entry

In one line

CLAUDE_CODE_DISABLE_THINKING
Set to 1, it leaves the thinking field out of each request.
MAX_THINKING_TOKENS
It sets how many tokens Claude may spend thinking.