# What changed with Claude Opus 5.5
The single biggest setting to retest: effort
Opus 5.5 runs at medium effort by default. Opus 5 used a higher default. Anthropic recommends that effort be the first lever you change when you want different speed, cost, or quality tradeoffs. In their internal tests, Opus 5.5 at medium effort matches or beats Opus 5 at high effort on coding and knowledge tasks.
Practical step: run the same prompts you used on Opus 5 against Opus 5.5 at multiple effort levels (lower, medium, higher) and measure latency, cost, and quality rather than assuming prior settings remain optimal.
Remove explicit "think carefully" instructions in chat
Practical step: for chat UIs, strip lines that explicitly instruct the model to deliberate and test response time and quality with and without them.
Lower effort before changing prompts
If you want the model to think less, try lowering the effort setting first rather than adding prompt instructions that ask for less thinking. Save very high effort like xhigh or max for tasks where you can demonstrate a real quality gain.
Practical step: build effort as a tunable parameter in your integration and make it easy to test different levels in QA.
Agent guidance: use time budgets and elapsed-time signals
Practical step: implement a task-level time budget and include elapsed-time metadata so agents prioritize within the budget.
Handling pasted external text
When users paste emails or other source text, Anthropic suggests wrapping that content with tags containing a random ID and a system note describing how Claude should treat the tagged text. Tags are plain text and copyable, so this is only one layer of defense against prompt injection.
Practical step: add textual tags plus handling notes for pasted content and treat them as a partial guardrail.
Other operational notes
- Output caps (max_tokens) may be consumed by the model's internal thinking process on Opus 5.5, which can truncate visible replies if you used an approach that relied on thinking being off. Re-check max_tokens behavior in your front-end flows.
Bottom line