Most of the coverage around Claude Opus 4.8 focused on benchmarks. The change that actually matters for how you work is getting almost no attention.
It shipped with effort controls. Four levels: Low, Medium, High, Max. You set the depth before Claude starts thinking.
That sounds like a minor UI option. It isn’t. It’s closer to the difference between asking a consultant to glance at something versus asking them to actually sit down and work through it. Same person, completely different output, because you told them upfront how much it matters.
The old way vs. the new way
Before 4.8, Claude applied roughly the same cognitive depth to everything. Proofreading a sentence got the same treatment as writing a pricing strategy. You had no say in how hard it actually thought.
In practice, this created a strange situation. You’d get over-engineered answers to simple questions and occasionally surface-level responses to genuinely complex problems. The model was guessing at stakes based on prompt length and tone, not because you told it anything useful about what was actually riding on the answer.
Now you do. And that changes two things at once:
- 🧠 You stop burning depth on tasks that don’t need it
- You start getting genuinely considered output on the ones that do
The discipline that makes this work: match effort to stakes. A quick email reply does not need the same processing as a positioning decision that affects your pricing for the next six months. Treating them the same was never logical. Now you don’t have to.
How to use the four levels
Low for things you’ll barely check. Formatting, quick factual answers, proofreading. If you’re just cleaning up a paragraph or converting a list into bullet points, Low gets it done faster and you don’t need Claude to consider edge cases it won’t find anyway.
Medium for most everyday writing and research. The default for routine tasks. A solid first draft of a newsletter section, a summary of a document, a quick competitor comparison. Enough depth to be useful, not so much that you’re waiting for something that didn’t need that much work.
High for complex drafts, multi-step analysis, anything feeding a bigger decision. Think: a sales email to an important prospect, a content brief where the angle actually matters, research that will inform something you’re building. These tasks have real consequences if the output is mediocre, so give it real effort.
Max for the 10% that genuinely matters. A pricing decision. A strategic plan. A client deliverable someone will actually act on. A positioning document your whole team will work from. When getting it wrong has real cost, stop treating it like a routine task.
⚡ The Max-effort prompt that works
When a task is actually high-stakes, here’s the structure to use:
This is a high-stakes task and I want your maximum effort. Do not rush it.
The task: [describe the decision or deliverable in full, including context, constraints, and what’s riding on it]
Before you answer:
- Reason through multiple approaches, not just the first one
- Consider what could go wrong with each
- Tell me where you’re confident and where you’re uncertain
- Flag any assumption that, if wrong, would change your answer
Then give me your most considered output.
Each piece of this prompt is doing something specific. “Do not rush it” signals that you want real deliberation, not a fast first draft dressed up as analysis. Describing the context and what’s riding on it gives Claude the information it needs to actually calibrate. Asking it to consider multiple approaches forces it past the first plausible answer, which is often not the best one. And asking it to flag uncertainty is where 4.8’s other major improvement becomes visible.
The “flag your uncertainty” instruction pairs with 4.8’s other major change: it’s now four times less likely to give a confident answer that’s quietly wrong. Anthropic’s internal testing scored it at 0% on uncritically accepting flawed results. That matters because the old failure mode wasn’t Claude giving obviously bad answers. It was Claude giving polished, confident answers that contained a wrong assumption buried three paragraphs in. You’d catch it only if you already knew enough to question it.
Max effort plus an explicit uncertainty request means you get real uncertainty flagging, not polished-sounding false confidence. The combination is what actually makes high-stakes output trustworthy instead of just impressively formatted.
The one habit worth picking up this week
Set effort to Max on your single most important task of the day. Set it to Low on everything routine. The output difference on what matters is immediate, and the habit compounds quickly. Within a week you’ll have a reliable intuition for where each level belongs, and your most important work will consistently get the depth it actually deserves instead of whatever the model guessed at.
That’s the real upgrade. Not the benchmark number. The ability to finally tell your AI how hard to think before it starts.
Claude Opus 4.8 launched two days ago with a feature most people are ignoring: you can now tell it how hard to think before it starts. It changes output quality more than the benchmark gains.
by u/Professional-Rest138 in PromptEngineering