- Should we move from Opus 4.8 to Opus 5?
- Almost always yes. Pricing is unchanged at $5 input and $25 output per million tokens, and Opus 5 is stronger across coding, reasoning, computer use, and alignment. We re-run the eval suite, document the diff, and switch the default model in a config change.
- Does Opus 5 replace Fable 5?
- Not entirely. Fable 5 is still the top tier. But Opus 5 comes within 0.5% of Fable 5 on coding and beats it on some computer-use tasks at a fraction of the cost, so it removes many of the reasons to pay Fable 5 rates. We route to Fable 5 only for the residual hardest work, and we prove that boundary on your tasks rather than assuming it.
- What is the context window?
- Opus 5 is a Claude 5-era model, so it carries the family's 1M-token context window and 128K maximum output, the same as Fable 5 and Opus 4.8. As always, retrieval and context hygiene beat filling the window, and we build for that.
- When does fast mode pay off?
- Two cases. First, latency-sensitive interactive paths such as chat UIs and in-app agents, where 2.5x output speed at 2x price is a worthwhile trade. Second, long-running asynchronous workflows where wall-clock time has a real business cost. For batch or cost-sensitive workloads, standard tier remains the right pick.
- Do the alignment numbers mean we can relax our own evals?
- No. Anthropic's alignment improvements are real and welcome, but model-level alignment does not replace task-specific evals on your data, your prompts, and your guardrails. We run the customer eval suite on every model change, every release.