Anthropic published its own numbers on how Claude Code sessions changed between March and September: context per request grew 2.6 times, the ratio of input to output tokens went from 189:1 to 324:1, and input that misses the cache fell by more than half. Claude now works 3.3 times longer per prompt, and API-key and cloud-provider users can set a one-hour cache lifetime themselves.

The caching mechanics moved on the API side the same week. OpenAI's GPT-6 caching update applies the discount to shared prefixes reused within 30 minutes, adds explicit cache breakpoints, and lets you change reasoning effort without breaking the cache. Anthropic added a beta that defines tools mid-conversation, so adding or changing a tool no longer invalidates the prompt cache. Anthropic's worked example puts numbers on it: 2.8M input tokens cost $11.20 uncached and $1.62 at a 90% cache hit rate, and an output token costs 100 times a cache read. For an agent that re-reads a long prefix every turn, the hit rate is now the line on the bill that moves most.

A correction to last issue: the same post says the lower Opus 5.5 price is passed on to Pro, Max and Team limits, including cached context, so they go about 25% further than on Opus 5. We wrote that Anthropic had not put a number on it.


From us

From the Yaw blog

Claude Code this week

The broader week