Anthropic just flipped Sonnet 5 into the default model for Claude Code — and did it with a 1M-token native context window and promotional pricing front-and-center. That single decision transforms a product-level change into an operational one: model selection is now an infra policy that affects token budgeting, routing fallbacks, and deprecation timing.
Anthropic made Sonnet 5 the default in Claude Code and documents a large context offering (on the order of one million tokens) for the Sonnet family. Promotional pricing was announced alongside the rollout; check Anthropic's official pricing and deprecation pages for the exact rates and end dates rather than relying on recollection or third-party posts. Anthropic also updated deprecation notices for older variants—consult the provider's deprecation dashboard for specific model IDs and retirement dates.
What matters operationally
This isn't just a model upgrade; it's a change in the default runtime contract for agentic and code-heavy workloads. Platform teams need to do three concrete things immediately:
- Treat defaults as runtime config: make Sonnet 5 an explicit, documented choice in service configs, CI runs, and feature flags instead of implicitly relying on provider defaults.
- Recalculate token budgets and SLOs: very large context windows change memory use, latency characteristics, and cost profiles. Promotional pricing can mask long-term economics—assume post-promo costs will be higher and set guardrails accordingly.
- Plan for deprecation cliffs: audit any embedded tooling, cached prompts, or serialized system messages that reference older Opus/Fable variants and have a migration plan for pinned model IDs.
Anthropic's lineup matters more than any single release. Sonnet 5 is positioned as a balanced, widely deployable workhorse optimized for code and agent workflows, not necessarily the research "frontier" variant. Treat it as the baseline for everyday agentic workloads and keep pinned access to frontier variants for capability-sensitive use cases.
Ecosystem ripple, not a headline rewrite
No major competing model launches dominated this week; instead, community inference stacks and agent frameworks (LangChain, LlamaIndex, vLLM, TGI, Ollama, llama.cpp, etc.) shipped minor point releases focused on performance and tooling. That underscores the point: provider defaults and deprecation schedules nudge the ecosystem more than single-model breakthroughs.
Anthropic's cadence means platform teams will see frequent upstream changes. If your routing, fallback, and cost-control logic assume a static model surface, you will be surprised. Use explicit model pins in infra configs and bake automated canary testing into model rollouts.
This is the right call, and also the one that will bite teams that ignore it. Making Sonnet 5 the default reduces fragmentation for agentic workloads and gives teams a consistent baseline with a huge context window. But defaults are now a deployment decision. If you still treat model selection like a library import, you're about to learn why infra teams exist.
Expect the next 90 days to be a migration sprint. Audit any persistent references to older Opus/Fable variants, add explicit pins to Sonnet 5 where you want the large context, and introduce cost guardrails tied to token volumes. Longer term, make model routing part of your platform API: route high-sensitivity, high-cost calls to pinned frontier variants and route general agent workloads to Sonnet 5.
If you want a short operational playbook, see our earlier coverage on Sonnet 5 and agentic defaults for practical checklists and templates.
Final thought: model defaults are the next config to be managed like CPU and memory. Providers will keep promoting new "workhorse" variants. The teams that win are the ones that treat those promotions as infra events—with pins, canaries, quotas, and a calendar linked to provider deprecation schedules.