On November 9, Anthropic's developer blog claude.dev published a selection guide by Addy Osmani, "Which Claude model should you build with?"; the ClaudeDevs post drew about 9,200 likes and 12,000 bookmarks. The core advice: start most coding and knowledge work on Opus 5.5 at medium effort (the Claude Code default); drop to Sonnet 5.5 for well-scoped bug fixes and spec-driven work; use Haiku 5.5 for classification, routing, extraction, and log-reading subagents; and move up to Fable 5.2 for major refactors, migrations, and deep research. Before switching models, tune effort and give the model a way to verify its own work. The guide also lists prices, default effort levels, and compatibility differences that can trigger 400 errors when migrating.
Key Takeaways
- ✓Prices (vendor figures, per million input/output tokens): Haiku 5.5 $0.10/$0.50 ($0.50/$2.50 above 100K), Sonnet 5.5 $2/$10, Opus 5.5 $4/$20, Fable 5.2 $8/$40; all four have a 1M context window and 128K max output
- ✓Anthropic's own FrontierCode 2.0 runs: Fable 5.2 at high scores 45.3% vs Opus 5.5 at max 45.5% for roughly half the cost per task, so test Fable before pushing Opus past high
- ✓On a SWE-bench Pro subset, running Opus 5.5 at low and re-running failures at high passed about 97% at about $0.17 per task, versus 95.3% at $0.29 with everything at high
- ✓An Opus 5.5 lead over up to 25 parallel Sonnet 5.5 workers searching about 22 million tokens of code cost about a third less than Opus alone, with a similar score
- ✓Migration traps: Fable 5.2 enables preserved thinking on all API accounts, so editing earlier context returns a 400; tool_choice any/tool also returns 400 on Sonnet 5.5, Opus 5.5, and Fable 5.2

Key Decision Metrics at a Glance
Heavy Claude Code use: compare subscription limits and API bills
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Core Background and Industry Pain Points
After Fable 5.2 and Mythos 5.2 launched, the Claude lineup has four generally available models, Haiku 5.5, Sonnet 5.5, Opus 5.5, and Fable 5.2, with input prices ranging 80x from $0.10 to $8 per million tokens. Many developers are unsure which to default to, so Anthropic published an official selection guide by Addy Osmani on claude.dev; the ClaudeDevs post passed 12,000 bookmarks.
Architecture Highlights and Underlying Mechanisms
The guide treats choice as two dials: model and effort. Start on Opus 5.5 at medium and raise to high if needed; beyond high, one more effort level can cost as much as a bigger model, so test the next model up at a lower effort instead. The prompt cache belongs to the model that wrote it, so the first turn after a switch pays cache-write again; run /compact first. Thinking blocks are readable only by the same or higher tier, so moving down loses earlier reasoning.
Authoritative Benchmarks and Measured Results
All figures are Anthropic's own runs (vendor figures): on FrontierCode 2.0, Fable 5.2 at high scores 45.3% vs Opus 5.5 at max 45.5% at about half the cost per task; on Terminal-Bench 3.0, Fable 5.1 at max scores 58.0% vs Opus 5.5 at high 58.9% with half the tokens; on SWE-bench Pro, Opus 5.5 at low with failures re-run at high passes about 97% at about $0.17 per task. No third party has reproduced these yet.
Developer Hands-On Guide
In Claude Code, set model: haiku on subagents or set CLAUDE_CODE_SUBAGENT_MODEL; the built-in Explore subagent now follows the session model, so define your own Explore subagent to keep it cheap. Before moving to Fable 5.2, keep history append-only, send tool_choice auto with strict tools, and read content blocks by type. Then compare score against spend on your own tasks at two or three effort levels before committing.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.