Anthropic's Fable 5 came back, and it changes how you run agent fleets. From what the model is, to the manager-model orchestration pattern, the cost math, refusal handling, long-horizon runs, production operations, and choosing your orchestrator.

Fable 5 is back after a US export-control suspension. What the Anthropic model is, the specs and refusal behavior to handle, and when to pick Opus 4.8.

Fable 5 agent orchestration with the manager-model pattern: a 1M-context orchestrator that delegates to cheaper workers via fan-out, pipelines and verify loops.

Agent fleet economics: one Fable 5 orchestrator plus Sonnet 5 workers beats an all-frontier fleet for most work. The cost math and the tokenizer caveat.

Fable 5 refusals return a 200 with stop_reason refusal, not an error. Detect them in every worker, fall back to Opus 4.8 and track refusal rate as a metric.

Long-horizon agents on Fable 5: what 1M context, 128K output, the memory tool, compaction and task budgets unlock, what is verified, and six projects to try.

Fable 5 agent fleet operations: 30-day retention limits, refusal-rate alerting, per-role effort tuning, observability and availability planning for production.

Fable 5 vs Opus 4.8 as your agent fleet orchestrator: a fair head-to-head with a decision matrix by run length, budget, compliance and refusal tolerance.

New tutorials, open-source projects, and deep dives on coding agents - delivered weekly.