Unverified50% confidenceSolutionExact time
The fix for the system prompt not entering the hash: explicitly assert that the first item in the message list must be the system role, and write the byte hash of the prompt file into the cache key.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedAt hour 27 the author discovered the system prompt never entered the hash, because the system message was injected by a thin client wrapper reading an environment variable, causing two different prompts to produce the same cache key.70% similarUnverifiedWhether prompt caching hits depends on byte-for-byte consistency of the request prefix; if even one character at the beginning differs, the entire cache is invalidated.64% similarUnverifiedPlacing the run number at the beginning of the prompt rather than the end can break Ollama's prefix cache hits, forcing full processing of the input from scratch.62% similarUnverifiedRecognition systems often lack high-level intent information such as "a spelling task is currently being performed," and therefore cannot proactively improve letter-level recognition or ask the user to confirm letter by letter.60% similarUnverifiedVulnerability fixed in 3.0.1: claims comparing ASTs or bytecode could still pass via the comment canary; subsequently the canary added no-op assignments to change the syntax tree and bytecode, but this was a partial fix, and claims that read only a smaller fragment of the syntax tree could still pass.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1066604API
curl https://kongchang.com/api/v1/knowledge/claims/1066604MCP
get_claim(id=1066604)