{"version":"2.1.286","anchor":"new-api-cache-keepalive-subsystem-with-telemetry-names-and","canonical_anchor":"new-api-cache-keepalive-subsystem-with-telemetry-names-and","heading":"Groundwork for keeping the prompt cache warm","tier":"soon","area":"Prompt Cache","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/new-api-cache-keepalive-subsystem-with-telemetry-names-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Groundwork for keeping the prompt cache warm\n\nClaude Code gained a cache keepalive part that can switch itself off for your login or for a while after a refusal\n\n**Unclear.** What starts the keepalive and whether it is switched on is not established.\n\n**What**\n\nClaude Code now contains a cache keepalive part. The prompt cache is where the model's service keeps recent conversation so it does not have to process it again. This part writes log lines starting with `[cache-keepalive]` and records its own events. If it is refused, it switches itself off either for the rest of your login or for a while.\n\n**Why**\n\nKeeping the cache warm would mean sending periodic requests, which could change how you use the API.\n\n- Area: Prompt Cache\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}