Unverified50% confidenceDecision RuleExact time
Under the continuation protocol, requests must remain completely identical, and each resend must include the content, system instructions and tools, because the token carries the hash of the original prompt.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedThe general principle for achieving cache hits is to keep the prefix of the request context as stable as possible, placing fixed content such as system prompts and tool definitions at the very front, with per-turn user input appended at the end.71% similarUnverifiedOne-time feedback can be written into a project rules file and solidified as a long-term constraint that must be followed with every modification.62% similarUnverifiedThe non-determinism in tool call ordering causes cache keys based on request body hashes to identify functionally identical requests as different requests, resulting in cache misses.61% similarVerifiedContinuous Batching adopts iteration-level scheduling granularity, allowing completed requests to be removed and new requests to be inserted upon each token generation completion.61% similarUnverifiedWorkflows can be saved via / commands and re-run deterministically, invoking the exact same sub-agent configuration each time.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1021152API
curl https://kongchang.com/api/v1/knowledge/claims/1021152MCP
get_claim(id=1021152)