Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-27 · high
Anthropic's new beta header, live since July 24, lets harnesses swap toolsets mid-run instead of pre-declaring every tool to protect the cache.
Why now: Anthropic dated the fix to July 24, closing a gap that's forced agent harnesses to pre-declare every tool and eat the token cost for ones they never call.
Anthropic shipped a beta header on July 24 that lets Claude swap tools mid-conversation without invalidating the prompt cache, per its API release notes.
Before this, changing an agent's tools mid-run reset the cache. Most harnesses responded by pre-declaring every tool a run might ever need, then eating the token cost for the ones that never got called. The header, mid-conversation-tool-changes-2026-07-01, works on four models: Fable 5, Mythos 5, Opus 4.8, and Opus 5.
Phase-scoped tool access stops being a tradeoff. You can hand an agent read-only tools during planning, then swap in write tools only after a human approves the plan. No cache rebuild at the handoff. That's the pattern I've wanted for a while and couldn't justify on cost. I'm rewiring my own dispatch around it.
The catch: Anthropic's notes don't say whether the savings hold if you swap tools more than once per conversation. They also don't say what happens to cache pricing on the turn where the swap itself happens. Anyone building multi-phase agents will find out fast.
My bet: phase-scoped toolsets become the default agent pattern, not an advanced option people bolt on later. Read-only until a human signs off on the write step. If your harness still declares every tool at session start, that's a decision to revisit.
Each link below shares sources, entities, or timing with this story.
PR #26062, "server: support MCP stdio," by ngxson, merged into ggml-org/llama.cpp on July 25 (r/LocalLLaMA). It landed alongside #26061 (vendored subprocess.h, merged July 24) and pwilkin's #26075 integration-and-tests PR. Until now, llama-server's web UI could only talk to MC...
43.3% on Frontier-Bench v0.1. Opus 4.8 scored 18.7%. That's not an incremental bump, that's the same benchmark with a different shape of answer. Anthropic released Claude Opus 5 on July 24 at $5/$25 per million input/output tokens, exactly half of Fable 5's $10/$50, while matc...
This is the most useful thing I read this week and it isn't close. Anthropic published its internal methodology for running large-scale code migrations with Claude Code on July 16, and unlike most engineering-blog playbooks, it carries receipts. Bun's Zig→Rust migration: rough...
Anthropic commissioned the independent evaluator to test 72 injection scenarios, held out from Anthropic, each run 10 times against Fable 5, Opus 5, and Sonnet 5 as of July 17. Clean sweep. TechCrunch has the details. A third-party held-out eval is a much stronger claim than i...
This one's been building for days and it crystallized this week. Per The Register, the incident behind the US export-control block on Anthropic's Fable 5 and Mythos 5 wasn't a jailbreak or a guardrail bypass. It was a plain three-word prompt, "fix this code," run against CVE-l...
Fable 5 and Mythos 5 went dark this week. Not a soft sunset with a six-month migration window. A US export directive, and within hours the models were unavailable to any foreign national anywhere on earth. Enterprise teams outside the US woke up to API calls failing against a...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.