Unverified50% confidenceFactExact time
Cline 4.1.0's Bedrock code places the cache point on the last message with role 'user', causing the cache point to never move forward as tool history grows, so users only see one cache write at the start of each session; version 4.0.12 works correctly.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/12/2026
First Seen
Valid until: 1/10/2027
Sources
Related Entities
Related Claims
Unverifiedv3.0.70 fixes the issue where Cline exited prematurely about 3 seconds after an MCP server or hook exited; the new version ensures that all input is fully read before exiting.64% similarUnverifiedThe location where the model edits the file in CLM affects prefix cache reuse: edits at the end of the file allow most of the cache to be reused, while editing from the middle causes content after that point to lose cache, increasing latency and cost.59% similarUnverifiedThe @cline/shared package has been updated to v0.0.91.57% similarUnverifiedv1.24.0 isolates subscription caching by backend so that cache confusion no longer occurs when switching backends, completed by contributor WoochLTW6.57% similarUnverifiedFor @cline/shared in the 0.0.x stage, it is recommended to use exact version numbers in package.json rather than ^ or ~ range specifiers to prevent automatic upgrades from triggering compatibility issues56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1006078API
curl https://kongchang.com/api/v1/knowledge/claims/1006078MCP
get_claim(id=1006078)