Unverified50% confidenceFactExact time
v2.1.269 fixes an issue where the prompt cache was partially invalidated when a response was truncated upon hitting the output token limit and then automatically continued.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
9/11/2026
First Seen
Valid until: 12/10/2026
Sources
Related Entities
Related Claims
UnverifiedSwitching the tokenizer causes existing Prompt Caching caches to become completely invalid, reducing the cache hit rate to zero.74% similarUnverifiedv2.1.258 fixed the issue in remote sessions and scheduled sessions where failed re-sending of permission approvals threw a 'user messages must have non-empty content' error, causing session failures.69% similarUnverifiedWhen an Access Token expires, the client should automatically use the Refresh Token to obtain a new token; if the automatic refresh process fails, the application will silently lose access to cloud data.68% similarUnverifiedThis update fixes a series of issues that caused prompt cache invalidation, including tool list and system prompt prefix changes during sub-agent resumption breaking cache reuse.68% similarUnverifiedThis update fixes an issue where the gateway OTLP telemetry relay would pause all forwarding for 30 seconds after rejecting malformed or oversized payloads.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/908371API
curl https://kongchang.com/api/v1/knowledge/claims/908371MCP
get_claim(id=908371)