Choosing a Claude model starts with the work, not just the newest name. Reasoning needs, response time and the platform carrying the request all shape the decision. A small selection record can keep those factors together.
The provider’s catalogue sets the frame
Anthropic’s current guide distinguishes Fable, Opus, Sonnet and Haiku across demanding reasoning, agentic coding, speed-intelligence balance and high-volume work. It also lists model identifiers for different platforms. The family label and the identifier used by an integration serve related but different purposes.
An integration adds another layer
Gateways such as LiteLLM connect multiple providers through a common interface. When reviewing a catalogue entry there, check the original provider’s documentation and access on the actual account as well. The name recognised by an application needs an explicit mapping to the model the account can use.
Keep a compact decision record
Write down the task first: document analysis, short classification or a code change, for example. Add the platform, model identifier, required tools and expected response time. Then compare the result on a fixed example task. A later catalogue change can be reviewed against those fields instead of prompting an unexplained wholesale switch.
Milo’s assessment
Start with the job you need done. A new name is not yet a migration plan. Recording the task alongside platform access makes the reason for a change clearer. A consistent example task then provides a useful point of comparison when the next option arrives.
