Extended Thinking — When Deeper Reasoning Pays Off
Extended thinking allows Claude to reason through a problem step by step before producing its final answer — an internal scratchpad that the model uses to explore approaches, spot errors in its own reasoning, and arrive at more reliable conclusions on hard problems. The feature is available on Claude 3.7 Sonnet and is activated by setting "thinking": {"type": "enabled", "budget_tokens": N} in your API call. The budget_tokens parameter controls how many tokens Claude is allowed to spend in its thinking process — a higher budget improves quality on harder tasks but increases latency and cost. Understanding when this trade-off is worth making is the key practical skill.
Task types where extended thinking reliably improves output quality
- Multi-step mathematical problems: Any calculation requiring more than two or three sequential operations benefits from extended thinking. Claude catches arithmetic errors during its reasoning trace in a way that it cannot when producing answers directly.
- Complex code debugging: When a bug involves multiple interacting systems, extended thinking lets Claude trace through the execution path systematically rather than pattern-matching to the most likely culprit.
- Strategic planning and trade-off analysis: Tasks that require considering multiple competing options and their downstream consequences — architecture decisions, risk assessments, business analysis — benefit from the extra reasoning space.
- Adversarial prompting resistance: On tasks where you need Claude to resist persuasion or identify flawed arguments (e.g. evaluating a business proposal with motivated reasoning baked in), extended thinking gives Claude room to notice the manipulation before responding.
Retrieval, format conversion, summarisation, and simple question-answering do not benefit meaningfully from extended thinking — and it adds latency and cost. Reserve it for tasks where the reasoning path itself is the hard part.