Claude Sonnet 5.5 shifts the focus from tokens to finished tasks

What was announced

Anthropic released Claude Sonnet 5.5 on September 28, 2026. Listed prices remained $2 per million input tokens and $10 per million output tokens. The company reported more than 30% faster output generation and up to 30% lower task costs through reduced token use.

The release also added cyber safeguards and fallbacks, with Medium effort as the default in Claude apps and Claude Code, and High on the Claude Platform. Anthropic positioned Opus 5.5 as stronger for complex work requiring sustained judgment. This retrospective examines the vendor's announcement, not an independent benchmark.

Source: Introducing Claude Sonnet 5.5

Analysis: Define what counts as finished

A cheaper attempt is not necessarily a cheaper result. A model could produce an answer quickly, yet leave enough cleanup that the complete job takes longer. Conversely, an answer that uses more computation might reduce revision work. The useful unit for an organization is therefore a result that meets a stated standard, with the resources required to reach it included in the accounting.

Consider a hypothetical request to produce a spreadsheet from a set of records. Completion might require accurate totals, traceable inputs, readable formatting, and a successful revision after one assumption changes. Counting only the first response would leave out several possible failure points. The quality threshold should be established before the comparison so that an attractive output does not quietly redefine what the task was supposed to accomplish.

Analysis: The denominator can change the verdict

An evaluation can report average cost per request, average cost per accepted result, or total spending for a batch of jobs. Those measures answer different questions. If difficult requests are abandoned, the first number may look appealing while concealing unresolved work. If a human fixes every mistake, the accepted-result measure needs to say whether that intervention is included.

A useful evaluation record would distinguish model consumption, tool activity, retries, and review effort. It would also preserve unsuccessful attempts. This is a proposed accounting framework, not a claim that the announcement used or omitted any particular method. The point is that an efficiency percentage becomes meaningful only when the reader understands which activities sit inside its boundary and what was counted as success.

Analysis: Effort settings are part of the experiment

A comparison between two models can accidentally become a comparison between two configurations. If one system is allowed to spend more time checking its work, a difference in speed or quality may reflect that choice. The configuration is not a minor footnote when it changes the amount of reasoning attempted.

For an illustrative evaluation, a team could first hold the task and acceptance criteria fixed, then compare several settings within its own time and cost constraints. The desired result would be a map of tradeoffs: where additional effort improves outcomes, where it adds little, and where the remaining errors require human judgment. That would support a more precise decision than declaring one setting universally best based on a blended score.

What remains unproven or unknown

The quoted speed and savings figures are Anthropic's claims. This article does not establish that a particular user will receive those gains, nor that the new safeguards resolve every possible misuse or reliability problem. The release's positioning also leaves room for different models to suit different work.

Missing from any reader's own decision is a measured connection between those claims and their tasks. Does an apparent saving survive difficult inputs? Does the model ask for clarification when a requirement is ambiguous? Does a faster answer preserve the details that make the result useful? Those questions need observed outcomes under disclosed conditions. They cannot be answered by converting a vendor percentage into an assumed budget reduction.

Source: Introducing Claude Sonnet 5.5

Practical implications: Keep a small, inspectable comparison

A bounded trial can begin with a handful of representative tasks and written acceptance criteria. The reviewer can record the configuration, initial result, corrections, and final decision for each task. Any consequential change in use would still need an appropriate review of observed results; this article makes no deployment recommendation.

The most informative result may be uneven. One category might improve while another remains difficult. Keeping that variation visible would help readers interpret the release as a set of testable propositions about useful work, rather than treating a lower projected bill as an outcome already achieved.