# Claude Fable 5.2 Migration: 4 Breaking Changes That Return 400 (and 2 Silent Defaults) > Source: > Published: 2026-11-11 03:33:15+00:00 Fable 5.2 has been out for two days: top of the benchmark table, 20% cheaper, and Copilot adopted it on day one. But Anthropic's official migration guide hides 4 breaking changes and 2 silent default changes. If you just swap the model ID and ship, your production traffic can start returning 400s. The key point: none of these four changes make the model worse. They make the request fail outright. Run the checklist below before you upgrade. Each thinking block is only valid for the system prompt, tools, and history it was issued with. Fable 5.1 enforced this only for accounts created after 2026-08-31. Fable 5.2 enforces it for everyone. The pattern old accounts used to get away with — rewriting an earlier turn mid-conversation and continuing — now returns `400 Invalid signature in thinking block`, and retrying does not help. The correct posture is append-only history. Test whether your pipeline secretly rewrites history with the test header first: ``` curl https://api.anthropic.com/v1/messages \ -H "anthropic-beta: thinking-binding-controls-2026-08-01" \ -d '{"model": "claude-fable-5-2", "prefix_mismatch_behavior": "drop_block"}' ``` Then turn on `input_transformations` logging and find which step is rewriting history. Routing, retries, and refusal fallbacks are standard agent plumbing — but Fable 5.1 and Opus 5.5 cannot read Fable 5.2's thinking blocks. When a fallback happens, the API silently drops those blocks. The request succeeds, but the next turn has lost its reasoning context, and cost and latency both go up. Do this instead: `reasoning effort` into Fable 5.2 messages — never into Fable 5.1 messages.`computer_20251124` is gone The old computer tool version field `computer_20251124` is retired. The replacement is `computer_toolset_20260801`. Skip the upgrade and you get a 400. Two details that trip people up: `computer_use_20260201`; the beta tool name is `computer-use-2026-01-14`.` computer_use_20260211` are two separate versions — fill them in separately. This is the easiest of the four to miss: the advisor must be from the same model family as the main model. Fable 5.2 only pairs with Fable 5.2 or Mythos 5.2 (beta name `mythos-advisor-5-2-20260115`). Using Opus 4.8 as the advisor returns a 400 directly. Three details: `model` and `advisor_model` fields to the same model. Fable 5.2 changed two defaults without telling you at upgrade time. `tool_choice` changed from `auto` to `required`. Under Fable 5.1 you could leave `effort` moved up a tier, from low to medium. The price math: Fable 5.2 is 20% cheaper than 5.1, but if your task only needed low effort, the higher default spends the discount right back. The fix: pin `low` for cheap tasks, `high` for hard ones. The official numbers: Fable 5.2 is $8/$40 per million tokens, down 20% from 5.1's $10/$50. Opus 5.5 is $4/$20 — half the per-token price. Per token, Fable is the expensive one; per task, it wins on long, hard work, because fewer steps mean fewer total tokens. The trap is the effort tier. Artificial Analysis scores Fable 5.2 at 62 on High effort vs 65 on Max — 3 points apart — while the Max tier runs about $26.50 per task, roughly 2.6x Opus 5.5, with a 216-second first token. High effort gets you nearly the same score for far less money and time. And the rate limit is separate: Fable 5.2's limit is independent of Fable 5.1's. Confirm your quota before you switch traffic, or you will get throttled on launch day. ``` 1. Pin the model ID to claude-fable-5-2 and pin effort explicitly 2. Confirm the workspace has 30-day data retention enabled 3. History is append-only; verify with the drop_block test header 4. Computer tool moved to computer_toolset_20260801 5. Advisor changed to Fable 5.2 / Mythos 5.2 6. tool_choice set to auto, with an explicit instruction 7. Handle stop_reason refusal; fallback targets are Opus 4.8 / Opus 5 only 8. Confirm Fable 5.2's independent rate limit 9. Re-run your own eval per effort tier before cutting over traffic ``` Which model are you running, and which of these 9 checklist items are you stuck on? Tell me in the comments and I'll help you think through the migration path. *Adapted from the Chinese original published on Juejin on 2026-11-11 ("Fable 5.2 迁移避坑：4 个会让你的代码报 400 的改动"). Same facts, restructured for dev.to readers. Facts checked against Anthropic's migration guide and the November 9 announcement on 2026-11-10/11.*