If you build with AI, last week moved the number that actually matters to you. Not a leaderboard position. What it costs to get the work done.
Anthropic released Claude Opus 5 on July 24. Five days later, on July 28, the Model Context Protocol shipped its largest revision since it launched. A day before the model landed, voice mode got the upgrade people had been asking about for a year. Almost all the coverage went to which model beat which other model on which chart. That framing skips the part that shows up on your invoice.
So let me put the verdict first. Opus 5 costs exactly what Opus 4.8 cost, at $5 per million input tokens and $25 per million output tokens. On Anthropic’s own Frontier-Bench v0.1 run, it more than doubles Opus 4.8’s score at a lower cost per task. Across six days, five other changes shipped, and every single one of them lowers the floor for people building without a platform team behind them. If you have been waiting for agent work to get affordable enough to try, that wait just got shorter.
Now the receipts.
The price stood still while the model moved
Anthropic’s launch post claims Opus 5 comes close to the frontier intelligence of Claude Fable 5 at half the price. The specific numbers behind that: on Frontier-Bench v0.1, Opus 5 surpasses all other models and more than doubles Opus 4.8’s performance at a lower cost per task. On CursorBench 3.2 at max effort, it lands within 0.5% of Fable 5’s peak score at half the cost per task.
Those are vendor-reported figures, and the footnote matters. Anthropic ran Frontier-Bench internally on the mini-SWE-agent harness with a GKE backend, averaging reward over five attempts per task. That is a disclosed methodology, which is better than most, but it is still the vendor grading the vendor.
For a counterweight, CodeRabbit ran Opus 5 against their own code review workload and published something more textured. They found effort behaves like a routing decision rather than a free upgrade, with x-high buying precision at a coverage cost, and nothing improving uniformly. They also measured roughly 60,500 input tokens per call against roughly 40,500 for the GPT-5.6 lanes doing the same job in the same runs. Bigger context in, longer answer out, and part of the cost premium lives right there.
Both things are true. The model is meaningfully better per dollar, and it will happily spend more dollars if you let it.
The effort dial is the actual cost lever
Opus 5 ships with an effort parameter at five levels: low, medium, high, xhigh, and max. The API defaults to high.
The interesting part is that Anthropic’s own prompting guide tells you to reach for less. It recommends starting at the default and then using low and medium liberally as your primary control for token cost and response time wherever quality holds, stepping up to xhigh only for demanding coding and agentic work. A vendor telling you to buy less compute is not a thing you see often, and it is worth taking them up on.
Two migration traps come with it. Thinking is now on by default, which is a behavioral break from Opus 4.8, where requests ran without thinking unless you asked. And thinking cannot be disabled at xhigh or max effort, where those requests return a 400 error. Because max_tokens caps thinking and response text together, anything you previously ran without thinking needs its limits revisited.
One more caution the docs are explicit about: changing effort between requests does not preserve cached prefixes from earlier turns. Pick a level at the start of a long session and stay there.
The quietest cost cut in the whole release
The minimum cacheable prompt length on Opus 5 dropped to 512 tokens, down from 1,024 on Opus 4.8.
That got about one sentence of coverage, and it is the change most likely to save a small builder real money. If your system prompt, tool definitions, or agent configuration sat just under the old threshold, they were uncacheable and you were paying full input price on every single call. Now they cache, with no code changes required.
Go add cache_control to the short system prompts you skipped last year. That is a fifteen minute job.
MCP stopped needing a server that remembers you
The 2026-07-28 spec moved MCP from a bidirectional stateful protocol to a request and response model. The initialize handshake is gone. The Mcp-Session-Id header is gone. Every request now carries its own protocol version and client capabilities.
In plain terms: any request can land on any instance. The sticky routing and shared session stores that horizontal deployments used to require are no longer a protocol requirement, and your connector can live on serverless or edge infrastructure like an ordinary HTTP workload.
That is the difference between hosting a connector for pocket change and hosting one on a cluster you have to babysit.
The release also brought Multi Round-Trip Requests, so a tool can pause mid-call to ask the user something and the client retries with the answer instead of holding a long-lived stream open. Routable transport headers let gateways and rate limiters route without parsing request bodies. Authorization now aligns with production OAuth 2.0 and OpenID Connect, which means MCP servers connect to enterprise identity systems like Entra or Okta without custom workarounds. MCP Apps and Tasks graduated into a formal versioned extensions framework.
Two honest caveats. This release contains breaking changes, with roots, sampling, and logging deprecated. And Anthropic’s own post says support is rolling out across Claude products soon, so the spec being live does not mean every Claude surface supports every piece of it today.
Claude Code got its agent teams back
This one has a plot twist that most roundups flattened.
On July 21, Claude Code v2.1.217 stopped subagents from spawning nested subagents at all. On July 24, v2.1.219 reinstated nesting at a default depth of three, controllable through the CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH environment variable. Three days from banned to bounded, which reads like a deliberate correction rather than a random default change.
The same release added Opus 5 as the default Opus model with its 1M token context, a workflowSizeGuideline setting that can now come from any settings file, a sandbox.network.strictAllowlist option that denies non-allowlisted hosts without prompting, a DirectoryAdded hook that fires when a new working directory joins a session, and mcp_server_errors in the headless init event so failed MCP configs stop being invisible.
Worth knowing that the workflow size guideline is advisory rather than an enforced cap. Dynamic workflows default to a medium guideline aiming for fewer than 15 agents. It nudges. It does not stop you.
The one release aimed at people who never open a terminal
Voice mode had been running on Haiku since Anthropic added hands-free conversation earlier this year, a choice made for speed. On July 23, Claude Opus and Claude Sonnet became available in voice mode, with a picker that switches models mid-conversation.
Two details make this more than a spec bump. Voice mode uses the fastest version of whichever model you select, so choosing Opus does not mean sitting through long pauses. And it defaults to the last model you used in text chat, which means a spoken commute session picks up where a typed desk session left off.
Voice can also reach the tools you have already connected. Anthropic names Gmail and Slack directly, and its own examples demonstrate pushing a Google Calendar meeting back by 30 minutes and turning a pitch conversation into a Canva one-pager. Claude asks permission before touching any of them.
The language expansion is the part that actually redistributes something. Anthropic lists eleven languages and gives every plan access to all of them, Free accounts included. Free also gets Haiku and one connected tool, while paid plans unlock the expanded models and every connector you have authorized.
Three caveats worth publishing. Claude does not auto-detect your language, and text-chat language settings do not carry over, so you set it in voice settings or ask out loud. Voice conversations count against your regular usage limits, so “available on every plan” is not the same as free to use heavily. And Anthropic names Opus, Sonnet, and Haiku for voice, with Fable absent from that list.
The feature is still in beta, still turn-based, and Anthropic says it works best from your phone.
Where this is still rough
Fast mode runs about 2.5 times default speed and costs $10 per million input tokens and $50 per million output tokens, which is double the base rate. It is also a research preview available on the Claude API only, not on Amazon Bedrock, Google Cloud, or Microsoft Foundry.
Mid-conversation tool changes and automatic fallbacks are both beta and both need explicit headers. Opus 5’s safeguards block binary-based vulnerability scanning, penetration testing, and exploit generation, so security practitioners will hit walls that the Cyber Verification Program exists to work around.
And a cheaper model at the same list price does not automatically produce a cheaper month. Reasoning models spend tokens thinking, and the effort ladder turns that spend into a decision you can quietly get wrong.
The bigger picture
Every one of these changes points the same direction, and it is not toward a smarter chatbot. Lower cache thresholds, an effort dial, stateless connectors, bounded agent nesting, fallbacks that route instead of failing, and the good models finally reaching the microphone on every plan. That is a stack getting cheap and predictable enough for people without infrastructure teams.
The exciting week is the one where the model wins a benchmark. The useful week is the one where the plumbing gets boring enough that a person building alone at their kitchen table can afford to run the same architecture a Fortune 500 runs. Last week was the second kind, and those weeks compound.
So What: your decision block
Do this now. Add cache_control to short system prompts you previously could not cache, since the 512 token minimum makes them eligible with no code changes. Then run an effort sweep on your own evals at low and medium before assuming you need high.
Skip this for now. Fast mode, unless a human is genuinely sitting there blocked. Double price across a long agentic run is a bad trade when nobody is waiting.
Try this today. Open voice mode on your phone, switch it to Opus, and talk through one decision you have been circling in text. It defaults to your last text model, so check the picker before you start.
Wait on this. Migrating production MCP servers to the new spec. The breaking changes are real, and Claude product support is still rolling out. Read the changelog, test in beta, move when your surface actually supports it.
One sentence to steal: Anthropic shipped a price cut and called it a model launch.
Sources
Introducing Claude Opus 5, Anthropic, July 24, 2026
What’s new in Claude Opus 5, Claude Platform Docs
Effort, Claude Platform Docs
Prompting Claude Opus 5, Claude Platform Docs
Context windows, Claude Platform Docs
The 2026-07-28 Specification, Model Context Protocol Blog, July 28, 2026
Key Changes: 2026-07-28, Model Context Protocol
Bringing MCP 2026-07-28 to Claude, Anthropic, July 28, 2026
Think through hard problems in voice mode, Anthropic, July 23, 2026
Claude Code Release v2.1.219, GitHub, July 24, 2026
Claude Code changelog, Claude Code Docs
Claude Opus 5 Benchmarks for AI Code Review, CodeRabbit (independent evaluation)
Claude Code subagent depth limits and budget caps, Digital Applied
Anthropic launches Opus 5, TechCrunch
Anthropic releases ‘more efficient’ Claude Opus 5, InfoWorld