{"version":"2.1.62","anchor":"optimized-prompt-cache-breakpoint-placement","canonical_anchor":"optimized-prompt-cache-breakpoint-placement","heading":"Optimized prompt cache breakpoint placement","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.62\/e\/optimized-prompt-cache-breakpoint-placement","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.62","markdown":"### Optimized prompt cache breakpoint placement\n\n**What**\n\nCache breakpoints are now applied to the last two messages in a conversation instead of only the final message, potentially improving cache hit rates with the Anthropic API.\n\n**Details**\n\n- Previously, only the very last message in a conversation received a cache breakpoint marker\n- Now the last two messages both receive cache breakpoints, increasing the likelihood of cache reuse when new messages are appended\n- The `skipCacheWrite` flag now only suppresses the breakpoint on the final message, leaving the second-to-last message always cached\n- This is an internal optimization; users may experience marginally faster response times due to improved cache utilization, but no action is required\n\n**Evidence**\n\nCache breakpoint logic in message preparation (search for `\"tengu_api_cache_breakpoints\"`) \u2014 `K$z()` at line ~519758"}