Claude Fable 5.1 Migration: Two Changes Can Break Agent Workflows

Breaking point one: forced tool choice

Anthropic documents that Fable 5.1 does not support forced tool selection. A request using tool_choice: {"type":"any"} or explicitly naming a tool returns an invalid_request_error with HTTP 400. auto and none remain supported.

This is easy to miss in an agent framework that silently injects forced choice after application code builds the request. Search serialized payloads, SDK middleware, routing layers, and stored prompt templates—not just the visible call site.

// Migration pattern: let the model choose, constrain the shape.
tool_choice: { type: "auto" }
// Pair with strict tool schemas or structured outputs where appropriate.

That pattern does not guarantee a tool call. If the workflow requires a specific deterministic operation, validate the model’s decision and handle a no-tool response explicitly. Do not retry the same invalid forced-choice payload.

Breaking point two: thinking-block compatibility

Fable 5.1 can read thinking blocks created by earlier Claude models. The reverse route is not compatible: earlier models cannot read Fable 5.1 thinking blocks. That makes a simple “try 5.1, then replay the full response to an older fallback” unsafe.

Anthropic says incompatible thinking blocks can be dropped when the relevant beta behavior is not enabled. With the beta header, transformations are recorded in input_transformations. Either way, the application should treat the route as a versioned transcript conversion, not as a transparent retry.

Keep conversation history append-only

Editing or deleting an earlier turn can invalidate the relationship between thinking blocks and the conversation that produced them. Redaction, summarization, memory compaction, and “helpful” message normalization therefore need tests.

Store an immutable raw transcript for replay and create a separate derived context when policy requires transformation. Record which messages were dropped, summarized, or redacted. A hash of the ordered input messages gives operations teams a way to detect a hidden mutation without storing more sensitive content in logs.

For workflows that browse, our Claude domain-allowlist guide separates access controls from source quality. The same principle applies here: a valid transcript is necessary, but it does not establish that a tool result is authoritative.

Run an eight-fixture migration gate

Download the Claude Fable 5.1 migration matrix (CSV). The included rows are marked EXAMPLE-REMOVE and describe tests to run; they are not production results.

1. Confirm forced named-tool and any requests fail before a tool can execute.
2. Test auto with one prompt that should call a tool and one that should not.
3. Validate strict schemas with valid and invalid arguments.
4. Replay an earlier-model transcript into 5.1.
5. Exercise the 5.1-to-older fallback path using a controlled transformation.
6. Edit a historical turn and confirm your guard rejects or rebuilds the context.
7. Verify that HTTP 200 responses with stop_reason: refusal do not enter the normal success path.
8. Test maximum elapsed time and cost controls on long-context jobs.

Treat refusal, retention, and price as separate controls

Anthropic documents that a refusal may arrive with HTTP 200 and stop_reason: refusal. A status-only health check can therefore record success while the application received no usable completion. Count transport success, model completion, refusal, tool success, and business success separately.

The documented price is $10 per million input tokens and $50 per million output tokens, with cache reads at $0.25 per million and cache writes at $12.50 for five minutes or $20 for one hour. Recalculate budgets from actual input, output, and cache telemetry; do not assume the larger context window should be filled.

Anthropic also documents 30-day retention and says Zero Data Retention is not the default unless expressly authorized. Verify the contract and product configuration for your account before sending sensitive data. Capability, cost, and retention are three independent release gates.

Roll out with a one-way canary

Begin with stateless or single-turn work. Then canary multi-turn conversations that stay on 5.1. Add cross-model fallback only after the transformation path passes. This order makes the incompatible direction visible instead of discovering it during an incident.

Pin the model ID, SDK version, tool schema version, transcript policy, and fallback model in the release record. The Claude search-result-blocks guide offers a compatible evidence pattern for tool-derived content.

Source, method, and update note

Primary sources: Anthropic’s Fable 5.1 migration notes and release notes, checked September 3, 2026.

Method: SearchEngineAnswer converted documented incompatibilities into an unrun migration matrix. We did not benchmark the model or execute production tools.

Recheck trigger: Update if Anthropic changes tool-choice support, thinking compatibility, retention, context limits, pricing, or refusal semantics.