# The Ultimate Guide to Claude Opus 4.7
**作者**: Paweł Huryn
**日期**: 2026-04-20T11:59:47.000Z
**来源**: [https://x.com/PawelHuryn/status/2046197132105769065](https://x.com/PawelHuryn/status/2046197132105769065)
---
The ten moves to make your 4.6 prompts work on 4.7, leading with context, and why you don't need more instructions.
4.6 guessed. 4.7 stopped guessing. Your old prompts still work, mostly. The ones that break need one of the ten moves below.
Anthropic shipped Claude Opus 4.7 on April 16. The official migration guide puts it plainly: 4.7 “takes the instructions literally” and “will not silently generalize.”
It's not a uniform upgrade. Wins on coding, creative writing, and structured work. Losses on instruction following in vague prompts, multi-turn, and long-context retrieval. The benchmarks show a trade, not a regression. I sort real regressions from preference artifacts and cost mechanics in § 6.
> Boris Cherny, Claude Code lead at Anthropic, posted on release day: "It took a few days for me to learn how to work with it effectively."
## Why Read This, and Why Now
Reddit calls 4.7 a regression. Arena shows 4.6 winning on instruction following. Anthropic's migration guide says it's working as designed. Boris confirms it's more agentic and precise.
The takes don’t agree because they’re measuring different workflows.
I’ve had 16+ hours with 4.7 so far. By the end you’ll know what's new, the ten moves to make your 4.6 prompts work on 4.7, and why you don't need more instructions.
## 1. What’s New in Opus 4.7
4.6 filled the gaps when your instruction was unclear. 4.7 takes you at your word.
For PMs: if your 4.6 workflow relied on the model “figuring out what you meant,” expect 4.7 to ask more questions, or to do less, or to do exactly what you asked for (which is not what you wanted).
## 2. Intent: The Universal Unlock
This is the principle: 4.7 rewards clear intent. Everything else in this post is a tactic.
Not longer prompts, not more rules, not a bigger CLAUDE.md. Intent splits into two layers:
- Strategic context is durable: what you’re building, who it’s for, what’s off-limits, what good looks like. Write it once. Put it in CLAUDE.md. It loads every session, progressive-disclosure style, so you’re not paying to reintroduce the project on turn one.
- Per-task intent is variable: what specifically do I want Claude to do right now. You still write this every turn. The gain from CLAUDE.md is that you stop retyping the strategic context on top of it.
> Treat Claude as a partner. Help it understand what and why you're doing, your strategy, objectives, and success criteria. Strategic context - not micromanaging the agent.
The full version (seven components, how they compose) is in The Intent Engineering Framework for AI Agents, published three months before 4.7 shipped.
This approach is aligned with Karpathy's claude coding post, too:
> "LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go (...) Change your approach from imperative to declarative to get the agents looping longer and gain leverage."
2.1 Anthropic and OpenAI convergence
Anthropic moved Opus 4.7 toward more literal instruction following. OpenAI updated their December 2025 Model Spec to say “consider not just the literal wording but the underlying intent.”
They’re converging from opposite directions. Anthropic is adding precision to its intent-first model. OpenAI is adding intent inference to its precision-first model. The same skill (engineering intent clearly) is becoming the unlock on both sides.
2.2 And Anthropic is already encoding it
Managed Agents (research preview) bakes success criteria and outcomes into the framework itself. I recently covered it here:
The skill of engineering clear intent is what transfers across vendors and models. That’s why it has the longest shelf life right now.
## 3. The 10 Claude Opus 4.7 Migration Moves
3.1 Front-load intent in CLAUDE.md
You don’t have to retype the strategic context every session. Put it in CLAUDE.md once. Every future session starts with the context already loaded. You still write per-task intent each turn, but you stop paying the “remember what we’re building” tax.
Delegate information the agent doesn’t have to read every session to other files, like strategy.md below:
Example: My context from CLAUDE.md
3.2 Default to Extra high (xhigh)
New effort level between high and max. Anthropic’s own recommendation for coding and agentic work.
Setting "Extra high" effort in VS Code Claude extension
max is prone to overthinking. Most “4.7 feels slow” reports trace back to people running max by reflex. Use max only when the problem actually needs deep reasoning.
3.3 Toggle effort mid-task
Effort is per-call, not per-session. max for the hard subproblem. Drop back to high for the rest.
3.4 Regression-test old prompts
New tokenizer. 1.0 to 1.35× more tokens per input. Your 4.6 workflows cost more on 4.7 before you’ve changed a line.
The offset to know about: Anthropic raised rate limits alongside the 4.7 launch:
My perspective: what matters most is cost per correct output token. Test it for your specific product before switching the model.
3.5 Batch questions. Stop drip-feeding.
If you have three questions, ask all three in one message.
On 4.6, clarifying across 3-4 turns worked. On 4.7, each turn adds reasoning overhead on top of literal interpretations from earlier turns.
Treat clarification as an exception, not a workflow.
3.6 Show what you want
Positive examples beat negative rules. According to Anthropic:
- “Like this: ” followed by short examples works.
- “Don’t do this: ” rarely lands and burns tokens trying.
Example: Positive examples from my personal agent
If your prompt has more than three “don’t” or “never” lines, flip them. What does the ideal output look like? Show two examples and cut the rules.
3.7 Delete old progress scaffolding
“Summarize every 3 tool calls.” “Give me a status update before moving on.” “Explain your plan, then execute.” Delete these.
Opus 4.7 emits high-quality progress updates natively in long agentic traces:
Example: Progress updates generated by my personal agent
3.8 Tell it to fan out explicitly
Opus 4.7 spawns fewer subagents by default and makes fewer tool calls per task. For parallel exploration, you now have to ask.
Phrasings that work: “spawn subagents in the same turn to investigate X, Y, Z.” Autonomy went up. Default delegation went down.
I also added separate instructions for Dispatch in DISPATCH.md. This file is referenced from CLAUDE.md:
Example: My instructions on how to spawn subagents
Later, I explain why I started using Dispatch less often.
3.9 Review plans, not diffs
Two different primitives. Don’t confuse them.
- Plan mode (Shift+Tab twice in the Claude Code CLI): inline, surfaces the plan before any code exists in the current session. Use for any change that touches more than one file:
Plan Mode in VS Code Claude extension
- /ultraplan (CLI only, doesn’t work in VS Code extension): cloud-based plan drafting from the CLI, review in the browser. Plan runs in a remote session while your terminal stays free:
/ultraplan in Claude Code terminal in VS Code
Why this matters more on 4.7: because 4.7 takes intent literally, a small misread in the plan becomes a large misread in the diff. Reviewing a 10-line plan for intent drift takes 30 seconds. Reviewing a 200-line diff for the same drift takes 15 minutes.
My take:
Intent drift compounds. Catch it in the plan.
3.10 Adaptive thinking only
Fixed thinking budgets are gone. Use thinking: {type: 'adaptive'} plus the effort parameter. Old API calls with budget_tokens return HTTP 400. Find and replace before flipping the model flag:
If you’re not an engineer, you don’t need to memorize the syntax. Just give your agent this documentation: https://platform.claude.com/docs/en/build-with-claude/adaptive-thinking.md (remove “.md” for a human-friendly view).
## 4. Closing
4.6 felt smart. 4.7 is honest. What looks like less intelligence is 4.7 refusing to guess.
Your leverage is clear intent. Not reviewing every line of code, writing endless instructions, or retyping the same context every session. The more of your intent and expectations you push up to CLAUDE.md, the less you pay (in money and attention) to run the thing.
P.S. Everything above is the mental model. In my Substack: 10 highest-ROI moves for 4.7 that actually move the bill, my remote setup, and Cowork/Dispatch gotchas.
## 相关链接
- [Paweł Huryn](https://x.com/PawelHuryn)
- [@PawelHuryn](https://x.com/PawelHuryn)
- [101K](https://x.com/PawelHuryn/status/2046197132105769065/analytics)
- [official migration guide](https://platform.claude.com/docs/en/about-claude/models/migration-guide#migrating-to-claude-opus-4-7)
- [posted on release day](https://x.com/bcherny/status/2044822408826380440)
- [The Intent Engineering Framework for AI Agents](https://www.productcompass.pm/p/intent-engineering-framework-for-ai-agents)
- [claude coding post](https://x.com/karpathy/status/2015883857489522876)
- [engineering intent](https://www.productcompass.pm/p/intent-engineering-framework-for-ai-agents)
- [here](https://x.com/PawelHuryn/status/2042008828334764162?s=20)
- [engineering clear intent](https://www.productcompass.pm/p/intent-engineering-framework-for-ai-agents)
- [take](https://x.com/PawelHuryn/status/2039622041960140878?s=20)
- [https://platform.claude.com/docs/en/build-with-claude/adaptive-thinking.md](https://platform.claude.com/docs/en/build-with-claude/adaptive-thinking.md)
- [In my Substack](https://www.productcompass.pm/p/claude-opus-4-7-guide)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [7:59 PM · Apr 20, 2026](https://x.com/PawelHuryn/status/2046197132105769065)
- [101.8K Views](https://x.com/PawelHuryn/status/2046197132105769065/analytics)
- [View quotes](https://x.com/PawelHuryn/status/2046197132105769065/quotes)
---
*导出时间: 2026/4/21 09:56:32*