Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.251 Home All releases olderv2.1.250
Claude Code v2.1.251

Cache-write cost estimates pick between a 1 hour and 5 minute TTL

You'll notice
Useful3 Signal2
Cost Tracking

Cost estimates now pick the cache lifetime that actually applied, so numbers match reality.

What

Cost estimation now chooses a one-hour cache lifetime when a longer-TTL override is configured or the request comes from the interactive session's main thread, and five minutes otherwise, so estimates match the cache tier actually used.

Evidence

return nM("repl_main_thread") ? "1h" : "5m";

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.251 →