This week delivered a familiar pattern: headline numbers that look good until you read the footnotes. Sonnet 5's apparent price parity hides a tokenizer change that breaks every cost projection you've built, and Node.js shipped a crash-on-input CVE that affects every active release line in production right now. Meanwhile, Zeta2.1 is one of the rare drops where the verdict is just "update and move on."
Claude Sonnet 5 launches with 30% higher token costs
Sonnet 5 matches Opus 4.8 benchmark performance at lower list prices than Opus, and replaces Sonnet 4.6 as Anthropic's mid-tier model. The catch: a new tokenizer inflates actual token counts by roughly 30% for English text. That means the list price comparison is meaningless until you recount your tokens against the new tokenizer. On top of that, adaptive thinking is enabled by default, which changes inference behavior in ways that can affect both output quality and latency in ways that aren't immediately obvious from the API surface.
The 1M context window and 128k output limit are unchanged. If your workloads are hitting Sonnet 4.6 capability ceilings, there's a real case for Sonnet 5. But if you're running cost-sensitive pipelines, you need to run your actual payloads through the new token counter before you touch anything in production—your token budgets and cost projections will be wrong the moment you switch.
