On this page3 sections
The restart instructions look straightforward until someone opens the newer note. A second copy of the data has not caught up with the first. Restarting must wait. In this illustrative situation, an engineer asks a model what to do next, and the important part of its answer is the part that interrupts the familiar procedure.
That makes a useful small comparison for Claude Opus 5.5: does the cheaper answer still keep the reason to wait? Anthropic’s release announcement lists $4 per million input tokens, $20 per million output tokens and $0.20 per million cache-read tokens. Tokens are the pieces of text the service processes and bills for. Anthropic reports a 40% saving over Opus 5 on typical workloads at default settings, not a guaranteed reduction for every team’s work.
The model is offered as claude-opus-5-5 on the Claude Platform and through AWS, Google Cloud and Microsoft Azure. Whichever route carries the request, compare it on the same job, with the application that will actually send the conversation.
Give both answers the awkward note
Put the runbook and the newer note in the same bundle for both configurations. The note describes a replication delay: the second copy is still catching up. Ask for the next action. An acceptable answer notices the conflict, retains the hold and says what would show that it is safe to proceed. A tidy explanation of the restart, on its own, has missed the decision.
It would be easy to clean up that bundle by removing the conflicting note. It would also remove the reason for the comparison. The earlier model-evaluation guidance follows this same distinction: an answer can sound plausible while recommending an action under conditions that do not permit it. Here, the awkward detail is exactly what the engineer needs the model to carry through.
Keep the supplied information, allowed tools and acceptance rule unchanged. Then count the work of getting an acceptable result as well as the tokens. If the engineer has to put the missing hold back into the conversation and ask again, include that effort. The lower price helps when it buys the answer the task required, not merely the first answer returned.
What happens when the engineer asks one more question?
Now the engineer asks, “What would show that the second copy has caught up?” The application sending this follow-up is the client. It carries earlier messages back to the model, and the previous response can also contain a reasoning block to carry forward, separate from the answer the engineer reads. Opus 5.5 cannot run with thinking disabled. Its preserved-thinking rules require that a reused block come from a compatible model and that the system instructions, tool definitions and preceding messages stay unchanged.
Appending the engineer’s question leaves that earlier conversation intact. Tidying an old instruction or replacing a tool definition does not. Those edits change the setting in which the block was produced, even if the client carefully preserves the block itself. A check of the preceding context, called the prefix check, can reject the mismatch; a configured alternative can drop the block and continue without it. The client needs to know which happened.
Opus 5.5 always checks that preceding context. What happens to a mismatch depends on how the client sends the request and which behavior it selects. Account age changes the default response, not whether the check runs.
For an ordinary request with mismatch behavior unset, an account created on or after 00:00 UTC on August 31, 2026 receives a 400 error: the request is rejected. On older accounts, failing blocks reach the model without that error. Message Batches, the route for submitting requests as a batch, handles the unset case differently. It drops failing blocks in the cases where an ordinary request would error, rather than rejecting the request that way.
A client can explicitly choose rejection or dropping through mismatch settings, which require the documented beta header. Check that choice and test the actual client before live use. A successful response alone does not show that it retained the earlier context. Then return to the engineer’s question and read the answer: did it keep the reason to wait? That remains a separate test.
Put the saving beside the decision it bought
Keep the earlier route available until the answer comparison and the client checks both work. Any production trial should then be bounded to the reviewed task and permissions. This is a proposed evaluation, not an independent Opus benchmark or a report of a model failing the fictional restart case.
Save the decision with the model configuration, client result and total cost. That gives the next person something more useful than a cheaper token rate: a record of whether less expenditure still produced an answer that noticed why the restart had to wait. The newer note stays in the bundle. It has earned its place there.
Sources & context
Sources linked in this article. Read alongside the author’s analysis; a citation does not independently verify a publisher’s claims.
- release announcementwww.anthropic.com
- preserved-thinking rulesplatform.claude.com
