cache-diagnostics changedbuild-with-claude/cache-diagnostics
Nearest release: v2.1.316, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−2removed
From line
3
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 3, old and new numbered
/
from line 3
33url: https://platform.claude.com/docs/en/build-with-claude/cache-diagnostics
44description: Diagnose unexpected prompt cache misses by comparing consecutive requests and identifying exactly where the prompt prefix diverged.
55featureMetadata:
6 status: ga
6 status: stable
77 zdr:
88 eligibility: qualified
99 note: Excludes [Covered Models](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention#model-specific-data-retention-requirements). Your prompts and Claude's outputs are not stored. A fingerprint of cryptographic hashes and token-count estimates is retained briefly to allow comparison against the next request.
from line 26
2626 - claude-opus-4-5-20251101
2727 - claude-sonnet-4-5-20250929
2828 supportedPlatforms:
29 Claude API: ga
29 Claude API: stable
3030---
3131
3232[Prompt caching](https://platform.claude.com/docs/en/build-with-claude/prompt-caching) cuts latency and cost significantly, but only when the beginning of your prompt is byte-for-byte identical to a recent request. A reordered tool, a timestamp interpolated into your system prompt, or an edit to an earlier message can silently invalidate the cache. Without cache diagnostics, the only signal is `usage.cache_read_input_tokens` dropping to zero, with no indication of what changed.
No line in this hunk matches that.