If a previous business used Haiku 4.5, this time it is not something that can go live just by changing the model name. Migrating to Haiku 5.5 involves five changes, each of which could cause requests to error out directly or return unexpected structures.
First, the budget_tokens manual thinking configuration errors out directly and must be changed to adaptive thinking plus the effort parameter. Second, temperature, top_p, and top_k are all locked to default values, so applications that rely on sampling parameters for creative control or diversified generation must change their logic. Third, assistant message prefilling is removed, so the previous approach of forcing JSON to start via prefilling must be replaced with tool calls or the structured output interface. Fourth, the computer operation tool version changes from computer_20250124 to computer_toolset_20260801, and both the interface format and return structure may differ. Fifth, adaptive thinking is enabled by default, so the first content block of a response may be a thinking block rather than the main text, and parsing logic must filter by the type field.
Anthropic provides a migration guide and recommends going through it before switching. Old businesses using Haiku 4.5 cannot go live by just changing the model name; they must rework the logic for thinking configuration, sampling parameters, prefilling, and tool versions.