Same list dollars. Lower dollars per task. Flip the workhorse this week.

On September 28, 2026, Anthropic released Claude Sonnet 5.5 (claude-sonnet-5-5), the second model in the Claude 5.5 family. Anthropic’s line: “It’s a clear upgrade over Claude Sonnet 5, runs 30%+ faster, and costs up to 30% less for most work.” List pricing stays at $2 / $10 per million input and output tokens, with cache reads at $0.20. Anthropic says the savings come from fewer tokens per task at the same sticker.
They position Sonnet 5.5 as the faster, lower-cost complement to Opus 5.5: Opus for complex work that needs careful judgment; Sonnet for well-scoped everyday and coding work. On Anthropic’s Terminal-Bench 4.0 numbers, Sonnet 5.5 scores 70.6% against Sonnet 5’s 10.3%. Those benches are Anthropic-reported. Independent reproductions are still settling. Treat them as vendor evidence, then remeasure on your own tasks.
Same calendar day, Claude Code v2.1.284 added Sonnet 5.5 and made it the default Sonnet model on the Anthropic API (1M context, same $2 / $10 list, $0.20 cache reads). Studios already on Claude Code may pick up 5.5 on upgrade without an explicit model pin. Audit model, availableModels, and deniedModels before the next client session.
Migrate thinking before you flip traffic
The platform migration guide is the how-to that saves you from silent 400s that look like a broken model.
On Sonnet 5.5, thinking: {"type": "disabled"} is gone. The docs error is explicit: "thinking.type.disabled" is not supported for this model. The lowest thinking setting is now thinking: {"type": "between_tools"}. Adaptive thinking (omit the field, or send thinking: {"type": "adaptive"}) is the default. Several other Sonnet 5 settings also return 400: forced tool choice (any / named tool), non-default sampling parameters, assistant prefills, and thinking budgets.
Checklist before production Sonnet traffic moves:
- Swap the model id to
claude-sonnet-5-5(no date suffix on the Claude API). - Replace
thinking: {"type": "disabled"}withthinking: {"type": "between_tools"}wherever you wanted thinking off up front. - Read content blocks by
type. Responses can open with thinking blocks;content[0].textbreaks. - Pass thinking blocks back unchanged in tool-use loops.
- Move forced tool use to
tool_choice: {"type": "auto"}plusstrict: trueon tools that need schema lock (Claude API / Google Cloud). On Bedrock, sendautowithoutstrictand validate in your code. - Set
output_config.effortdeliberately. Claude Platform defaults to High; Claude apps and Claude Code default to Medium. Re-run your effort sweep. Levels are recalibrated versus Sonnet 5. - Optional: in Claude Code, run
/claude-api migrate this project to claude-sonnet-5-5and verify the checklist it prints.
Do the migration on a staging route first. Then flip.

Route Opus for judgment, Sonnet for scoped work
Keep the two-lane map simple:
- Opus 5.5 for architecture, open-ended judgment, and multi-hour design calls.
- Sonnet 5.5 for scoped implementation, bug fixes, reviews, docs, slides, and everyday agent loops.
Anthropic’s own framing matches that split. Early tester quotes on the product page describe Sonnet 5.5 clearing higher-tier quality bars on well-bounded work while using fewer tokens and fewer steps. Keep the routing table in the harness. Leave the vendor quotes on the product page.
If you still pin Sonnet 5 on purpose, write that out in the harness config. A silent pin that blocks the new default becomes next week’s mystery.

Measure dollars per task
List price did not move. Cost per task did, if Anthropic’s testing holds on your workloads. Log three tasks you already know: one migration-sized, one review-sized, one volume loop. For each route and effort level, record dollars, steps, retries, and rework minutes.
Tokens alone hide effort and cache effects. Medium effort is the default in Claude Code and the apps; High is the platform default. Sweep both before you rewrite retainer floors. Pair this with last cycle’s reprice note: Reprice your agent stack in one afternoon.
Optional short: honesty after a failed tool
Failure-Transparent Agents (FTA) is a Sep 28 arXiv preprint. The authors’ line: “Tool-using agents can fail twice: a required tool can fail, and the agent can then report success without the evidence needed to justify it.” Add a post-failure arm to client evals: when a required tool fails, the agent must not claim success without evidence. Score that check apart from pass rate. Preprint only; not a lab product release.
Also on the desk
- Reprice your agent stack in one afternoon. Defaults and cost-per-task after the Sep 21–22 frontier price moves.
- The agent seat is a control plane. Identity, permissions, approvals under the commercial seat.
If you want Sonnet 5.5 defaulted, thinking migrated, and cost-per-task metering wired into a governed AI development seat, Start your build or write hello@mail.22atlas.com.
Linked sources
- Anthropic: Claude Sonnet 5.5 (2026-09-28)
- Anthropic GitHub: Claude Code v2.1.284
- Claude Platform Docs: Sonnet 5.5 migration guide
- Claude Platform Docs: Sonnet 5.5 overview
- arXiv preprint: Failure-Transparent Agents (FTA)
- Related Field note: Reprice your agent stack in one afternoon
- Related Field note: The agent seat is a control plane
Get our Articles and posts by email.
Up to one email a day with new Articles and posts from 22atlas.com and sean-weldon.com, plus occasional news about 22Atlas services.
Also on the desk
Technique
Reprice your agent stack in one afternoon
Sep 21–22 stacked three frontier ships and a price cut. Pick this week’s default for billable agent work, then remeasure cost per task before your retainer still prices last month’s floors.
Playbook
The agent seat is a control plane
Keep the agent seat for identity, permissions, approvals, and client context. Invoice a governed seat plus an Outcome Spec: setup, retainer, accepted work, and usage rails.