Effort
Control how many tokens Claude uses when responding with the effort parameter, trading off between response thoroughness and token efficiency.
Usage differs by product
output_config.effort on the request. With no value, the model’s default level applies.effort on the agent’s model object, or in a session’s model override. With no value, Managed Agents fills in the model’s default.The effort parameter lets you control how many tokens Claude spends when responding to requests. You can trade off between response thoroughness and token efficiency with a single model.
Set the effort level
Set output_config.effort on the request. The following example runs one request at medium effort.
client = anthropic.Anthropic()
response = client.messages.create(
model="claude-opus-5-5",
max_tokens=4096,
messages=[
{
"role": "user",
"content": "Analyze the trade-offs between microservices and monolithic architectures",
}
],
output_config={"effort": "medium"},
)
for block in response.content:
if block.type == "text":
print(block.text)How effort works
Most Claude models default to high effort, spending as many tokens as needed for excellent results; Claude Opus 5.5 and Claude Haiku 5.5 default to medium. You can raise the effort level to max for the absolute highest capability, or lower it to be more conservative with token usage, optimizing for speed and cost while accepting some reduction in capability.
The effort parameter affects all tokens in the response, including:
- Text responses and explanations
- Tool calls and function arguments
- Thinking (when active)
Because effort applies to every output token, it works with or without thinking. Lower effort also means fewer and terser tool calls.
Effort levels
| Level | Description | Typical use case |
|---|---|---|
max | Absolute maximum capability with no constraints on token spending. Available on Claude Fable 5.2, Claude Mythos 5.2, Claude Fable 5.1, Claude Mythos 5.1, Claude Fable 5, Claude Mythos 5, Claude Mythos Preview, Claude Opus 5.5, Claude Opus 5, Claude Opus 4.8, Claude Opus 4.7, Claude Opus 4.6, Claude Sonnet 5.5, Claude Sonnet 5, Claude Sonnet 4.6, and Claude Haiku 5.5. | Tasks requiring the deepest possible reasoning and most thorough analysis |
xhigh | Extended capability for long-horizon work. Available on Claude Fable 5.2, Claude Mythos 5.2, Claude Fable 5.1, Claude Mythos 5.1, Claude Fable 5, Claude Mythos 5, Claude Opus 5.5, Claude Opus 5, Claude Opus 4.8, Claude Opus 4.7, Claude Sonnet 5.5, Claude Sonnet 5, and Claude Haiku 5.5. | Long-running agentic and coding tasks (over 30 minutes) with token budgets in the millions |
high | Spends as many tokens as the task needs for excellent results. The default on every model that supports effort except Claude Opus 5.5 and Claude Haiku 5.5. | Complex reasoning, difficult coding problems, agentic tasks |
medium | Balanced approach with moderate token savings. The default on Claude Opus 5.5 and Claude Haiku 5.5. | Agentic tasks that require a balance of speed, cost, and performance |
low | Most efficient. Significant token savings with some capability reduction. | Simpler tasks that need the best speed and lowest costs, such as subagents |
Not every model that supports max supports xhigh.
The per-model recommendations that follow override this table where they differ.
Recommended effort levels
Differs by model
Claude Fable 5.2 supports all five effort levels. The API default is high. Adaptive thinking is always on, so effort is your main control for thinking depth, latency, and cost.
Start with high. Most of the gain in capability is already present at high, and above it, gains are uneven and depend on the task. Step up to xhigh for your hardest long-running coding and agentic work, where you’ve measured a gain. Step down to medium or low where your evals show quality holds. Reserve max for measuring the model’s ceiling and for the rare task where time and tokens don’t matter. At max the model optimizes for capability without regard to token cost. It runs slower and costs more than at xhigh, often for only a small gain.
Run an effort sweep on your own evals rather than carrying settings over from Claude Fable 5.1. At high and above, set a large max_tokens. It’s a hard limit on total output (thinking plus response text). Effort barely changes how long the model’s replies are, so use your prompt to change reply length and tone.
The same recommendations apply to Claude Mythos 5.2.
On supported platforms, Claude Fable 5.2 and Claude Mythos 5.2 also support changing effort mid-conversation with a per-message output_config, which preserves the prompt cache.
See also: Prompting Claude Fable 5.2
Claude Opus 5.5 supports all five effort levels, and medium is the default. Claude Opus 5 and earlier Opus models default to high, so a request that omits effort runs one level lower on Claude Opus 5.5.
Adaptive thinking is always on and can’t be turned off, so effort is the primary control for how much the model reasons and what a request costs. Requests that set thinking: {"type": "disabled"} return a 400 error at every effort level.
Run an effort sweep on your own evals rather than carrying settings over from an earlier model. At xhigh or max, set a large max_tokens. It’s a hard limit on total output (thinking plus response text).
Claude Opus 5.5 also supports changing effort mid-conversation with a per-message output_config, which preserves the prompt cache.
See also: Prompting Claude Opus 5.5
Claude Sonnet 5.5 supports all five effort levels, and high is the default on the Claude API. Its levels are calibrated differently, so a level doesn’t produce the same amount of thinking as on Claude Sonnet 5. Run a fresh effort sweep on your evals rather than carrying over the setting you used on Claude Sonnet 5.
Start with high unless your workload is agentic or latency-sensitive. For agentic coding and multistep tool use, start with medium for well-specified tasks and move to high for harder or longer ones. For chat and other latency-sensitive work, start with medium or low. Use xhigh or max only where your evals show a quality gain.
Set max_tokens with room for thinking and the reply. Thinking counts toward max_tokens even when the thinking content isn’t returned. For agentic coding, set max_tokens to 128,000, the model’s maximum, and stream the response (see Streaming messages).
To have the model respond without thinking first, send thinking: {"type": "between_tools"}, not "disabled". It works at low, medium, and high effort. At xhigh or max it returns a 400 error, so use adaptive thinking, the default, at those levels. See Running without up-front thinking.
On supported platforms, Claude Sonnet 5.5 also supports changing effort mid-conversation with a per-message output_config, which preserves the prompt cache. With between_tools, effort can’t change mid-conversation: a per-message output_config.effort at a different level returns a 400 error. To vary effort for each turn, use adaptive thinking.
See also: Prompting Claude Sonnet 5.5
Claude Haiku 5.5 supports all five effort levels, and medium is the default. Effort is the main control for how much the model thinks, and with it quality, latency, and cost. Start with medium for most work, including agentic coding. Use low, the cheapest and fastest level, for chat, short tool tasks, and simple, high-volume requests. In long agent prompts, the model is more likely to skip a search, stop early, or skip a check at low. Use high for knowledge work, longer agent tasks, and strict instruction following. Use xhigh or max only where your evals show a quality gain, and compare them with Claude Sonnet 5.5 on performance, cost, and speed. Thinking is on by default and counts toward max_tokens, so leave room for it.
To get less thinking, lower the effort level. You can also send thinking: {"type": "disabled"} at high effort or below. At xhigh or max, it returns a 400 error, so use adaptive thinking there: omit the thinking field or send thinking: {"type": "adaptive"}.
On supported platforms, Claude Haiku 5.5 also lets you change effort mid-conversation with a per-message output_config, which preserves the prompt cache. With thinking: {"type": "disabled"}, effort can’t change mid-conversation: a per-message output_config.effort at a different level returns a 400 error. To vary effort for each turn, use adaptive thinking.
See also: Prompting Claude Haiku 5.5
Claude Fable 5.1 supports all five effort levels. Start with high, the default. Step up to xhigh or max for the most capability-sensitive agentic and coding work, and step down to medium or low for routine or latency-sensitive work once your evals show quality holds. At high and above, set a large max_tokens. It’s a hard limit on total output (thinking plus response text).
Claude Fable 5.1 also supports changing effort mid-conversation with a per-message output_config, which preserves the prompt cache.
See also: Prompting Claude Fable 5.1
Effort is the primary control for trading off intelligence, latency, and cost on Claude Fable 5. Start with high, the default, for most tasks, use xhigh for the most capability-sensitive workloads, and step down to medium or low for routine work. Lower effort settings on Claude Fable 5 still perform well and often exceed xhigh performance on prior models. At high and xhigh, set a large max_tokens. It’s a hard limit on total output (thinking plus response text). See Cost control.
Reduce effort if a task completes but takes longer than necessary, or if you want a faster, more interactive working style.
See also: Prompting Claude Fable 5
Claude Opus 5 supports all five effort levels. Start with high, the default, and adjust based on your evals: step up to xhigh for demanding coding and agentic work, or to max when a task justifies unconstrained token spending. Use low and medium liberally as your primary control for token cost and response time wherever your evals show quality holds. If you carried effort settings over from an earlier model, run a fresh effort sweep on your evals rather than reusing them.
Effort controls thinking volume, not visible response length: on Claude Opus 5, changing effort does not reliably shorten responses, so prompt for length instead.
The API default is high. Set effort explicitly to use a different level. The value you pass overrides the default.
On Claude Opus 5, thinking cannot be disabled at xhigh or max effort: requests that set thinking: {"type": "disabled"} at those levels return a 400 error. See Effort with thinking.
When running Claude Opus 5 at xhigh or max effort, set a large max_tokens so the model has room to think and act across subagents and tool calls. Starting at 64k tokens and tuning from there is a reasonable default.
On supported platforms, Claude Opus 5 also supports changing effort mid-conversation with a per-message output_config, which preserves the prompt cache.
See also: Prompting Claude Opus 5
The guidance for Claude Opus 4.7 also applies to Claude Opus 4.8. Start with xhigh for coding and agentic use cases, use high for most other intelligence-sensitive workloads, and step down to medium or low only when you’ve measured that the lower level holds quality on your evals.
The API default is high. Set effort explicitly to use a different level. The value you pass overrides the default.
When running Claude Opus 4.8 at xhigh or max effort, set a large max_tokens so the model has room to think and act across subagents and tool calls. Starting at 64k tokens and tuning from there is a reasonable default.
See also: Prompting Claude Opus 4.8
Start with xhigh for coding and agentic use cases, and use high as the minimum for most intelligence-sensitive workloads. Step down to medium for cost-sensitive workloads, or up to max only when your evals show measurable headroom at xhigh.
The API default is high. To use xhigh, set effort explicitly. The value you pass overrides the default.
- Low effort: Efficient, but best for short, scoped tasks. Pair
lowwith explicit checklists if your task has multiple sections. - Medium effort: The setting for the average workflow where you want good results while reducing costs.
- High effort: Advanced use cases that still need a balance of intelligence and token consumption. This is often the best balance of quality and token efficiency.
- Xhigh effort: The recommended starting point for coding and agentic work, and for exploratory tasks such as repeated tool calling, detailed web search, and knowledge-base search. Expect meaningfully higher token usage than
high. - Max effort: Reserve for frontier problems. On most workloads
maxadds significant cost for relatively small quality gains, and on some structured-output or less intelligence-sensitive tasks it can lead to overthinking.
Claude Opus 4.7 also respects effort levels more strictly than Claude Opus 4.6, especially at low and medium. At lower effort levels, the model scopes its work to what was asked rather than doing more than requested. If you observe shallow reasoning on complex problems with Claude Opus 4.7, raise effort rather than prompting around it. If you must keep effort low for latency, add targeted guidance such as “This task involves multistep reasoning. Think carefully before responding.”
When running Claude Opus 4.7 at xhigh or max effort, set a large max_tokens so the model has room to think and act across subagents and tool calls. Starting at 64k tokens and tuning from there is a reasonable default.
See also: Prompting best practices
Claude Sonnet 5 defaults to high effort on the Claude API and Claude Code.
- High effort (default): Suitable for complex reasoning, coding, and agentic tasks where quality matters more than speed or cost.
- Xhigh effort: For the hardest coding and agentic tasks.
- Medium effort: Cost-saving step-down from the default. Comparable to Claude Sonnet 4.6 at high effort.
- Low effort: For high-volume or latency-sensitive workloads. Suitable for chat and non-coding use cases where faster turnaround is prioritized.
- Max effort: For tasks requiring the absolute highest capability with no constraints on token spending.
See also: Prompting Claude Sonnet 5
Claude Sonnet 4.6 defaults to high effort. Set effort explicitly to avoid unexpected latency:
- Medium effort (recommended): Best balance of speed, cost, and performance for most applications. Suitable for agentic coding, tool-heavy workflows, and code generation.
- Low effort: For high-volume or latency-sensitive workloads. Suitable for chat and non-coding use cases where faster turnaround is prioritized.
- High effort: For complex reasoning and tasks where quality matters more than speed or cost.
- Max effort: For tasks requiring the absolute highest capability with no constraints on token spending.
See also: Prompting best practices
Effort with tool use
When using tools, the effort parameter affects both the explanations around tool calls and the tool calls themselves. Lower effort levels tend to:
- Combine multiple operations into fewer tool calls
- Make fewer tool calls
- Proceed directly to action without preamble
- Use terse confirmation messages after completion
Higher effort levels might:
- Make more tool calls
- Explain the plan before taking action
- Provide detailed summaries of changes
- Include more comprehensive code comments
Effort with thinking
The thinking parameter controls whether Claude thinks in thinking blocks before answering; the effort parameter controls how much work Claude puts into the whole response, which in adaptive mode includes how often and how deeply it thinks. Don’t pass adaptive as an effort value: adaptive is a thinking mode, not an effort level.
At higher effort levels, Claude thinks more readily and at greater length. In a tool-use loop, follow-up requests that only process tool results can still skip thinking at any level. At lower levels, Claude can skip thinking entirely for simpler problems. See Thinking and effort for full guidance on how the two controls work together.
On Claude Opus 4.5, the only extended-thinking-only model that supports effort, it works alongside budget_tokens: set the effort level for your task, then set the thinking token budget based on how much reasoning depth the task needs.
For per-model thinking availability, see the per-model configuration table. Effort works with or without thinking. See How effort works.
Change effort mid-conversation
You can run later turns of a conversation at a different effort level in two ways. A per-message effort change keeps the prompt cache. A new top-level value on the next request can invalidate all or part of the prompt cache.
Per-message effort
Per-message effort sets a new level with a system message in messages.
Top-level effort on the next request
The top-level output_config.effort applies to the whole request. To run a later part of a conversation at a different level, set the new value on the next request. Because top-level effort shapes the rendered prompt, changing it between requests can invalidate cached prefixes from earlier turns. If you rely on prompt caching across a long session and your model doesn’t support per-message effort, pick an effort level at the start and keep it constant.
Best practices
- Set effort explicitly: The API defaults to
high(mediumon Claude Opus 5.5 and Claude Haiku 5.5), but the right starting point depends on your model and workload. - Use low for speed-sensitive or simple tasks: When latency matters or tasks are straightforward, low effort can significantly reduce response times and costs.
- Test your use case: The impact of effort levels varies by task type. Evaluate performance on your specific use cases before deploying.
- Consider dynamic effort: Adjust effort based on task complexity. Simple queries might warrant low effort, whereas agentic coding and complex reasoning benefit from high effort. See the next item before varying it within one conversation.
- Hold top-level effort constant within cached conversations: Changing the top-level effort value between requests can invalidate all or part of the prompt cache, so vary it across workloads rather than within a conversation that relies on cache hits. On models that support it, use a per-message effort change instead, which preserves the cache. See Thinking and prompt caching.
Next steps
Give Claude an advisory token budget for the full agentic loop to help the model self-regulate on long agentic tasks.
Understand adaptive thinking, where Claude determines when and how much to think, and steer it with effort and prompting.
Understand how thinking works, when Claude thinks by default, and how thinking interacts with effort.
Availability
Claude API
- APIs
- Messages API
- Managed Agents
- Models
- Claude Fable 5.2, Fable 5.1, Fable 5
- Claude Mythos 5.2, Mythos 5.1, Mythos 5, Mythos Preview
- Claude Opus 5.5, Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, Opus 4.5
- Claude Sonnet 5.5, Sonnet 5, Sonnet 4.6
- Claude Haiku 5.5
Amazon Bedrock
- API
- Messages API
- Models
- Claude Fable 5.1, Fable 5
- Claude Mythos 5.1, Mythos 5
- Claude Opus 5.5, Opus 5, Opus 4.8, Opus 4.7
- Claude Sonnet 5.5, Sonnet 5
- Claude Haiku 5.5
Amazon Bedrock (bedrock-runtime)
- API
- Messages API
- Models
- Claude Fable 5.2
- Claude Mythos 5.2
- Claude Opus 4.6, Opus 4.5
- Claude Sonnet 4.6
Claude Platform on AWS
- APIs
- Messages API
- Managed Agents
- Models
- Claude Fable 5.2, Fable 5.1, Fable 5
- Claude Opus 5.5, Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, Opus 4.5
- Claude Sonnet 5.5, Sonnet 5, Sonnet 4.6
- Claude Haiku 5.5
Claude Models on Google Cloud (Anthropic managed)
- API
- Messages API
- Models
- Claude Fable 5.2, Fable 5.1, Fable 5
- Claude Mythos 5.2
- Claude Opus 5.5, Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, Opus 4.5
- Claude Sonnet 5.5, Sonnet 5, Sonnet 4.6
- Claude Haiku 5.5
Claude Models on Google Cloud (Google managed)
- API
- Messages API
- Models
- Claude Fable 5.2, Fable 5.1, Fable 5
- Claude Mythos 5.2, Mythos 5.1, Mythos 5
- Claude Opus 5.5, Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, Opus 4.5
- Claude Sonnet 5.5, Sonnet 5, Sonnet 4.6
- Claude Haiku 5.5
Microsoft Foundry (hosted on Azure)
- API
- Messages API
- Models
- Claude Opus 5.5, Opus 5, Opus 4.8
- Claude Sonnet 5.5, Sonnet 5
- Claude Haiku 5.5
Microsoft Foundry (hosted on Anthropic)
- API
- Messages API
- Models
- Claude Fable 5.2, Fable 5.1, Fable 5
- Claude Mythos 5.2, Mythos 5.1, Mythos 5
- Claude Opus 5.5, Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, Opus 4.5
- Claude Sonnet 5.5, Sonnet 5, Sonnet 4.6
- Claude Haiku 5.5
Data handling
Data handling overviewApplicable endpoints
/v1/messageswitheffort
Excludes Covered Models
Was this page helpful?