Unverified60% confidenceFactExact time
Prompt caching uses a strict prefix-matching strategy; once a mismatch occurs at a given position, all cached content after that position is invalidated.
2
Sources
60%
Confidence
Long-term
Relevance
8/15/2026
First Seen
Sources
Related Claims
UnverifiedPrompt caching has a strict prefix-matching requirement: once the content or order of the tool list changes, the cache immediately becomes invalid, and all content after the prefix must be recomputed at the original price.75% similarUnverifiedPrompt caching matches an identical token sequence backward from the beginning of the prompt, and the matched portion receives the discount; once the tokens diverge, subsequent content is billed at full price.69% similarUnverifiedmloda performs per-candidate exception isolation on the matching hook of each candidate plugin, so an exception thrown by a single plugin will not interrupt the entire diagnostic report.68% similarUnverifiedCache matching typically requires an exact prefix match (including the token sequence), which is why developers need to place stable content at the front of the prompt and keep the order unchanged.67% similarUnverifiedFor example, when matching a123b456b with a.*b, .* first swallows up to the last b, and if the overall match succeeds, it does not backtrack.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/753255API
curl https://kongchang.com/api/v1/knowledge/claims/753255MCP
get_claim(id=753255)