{"version":"2.1.288","anchor":"resumed-session-cache-touches-gated-by-setting","canonical_anchor":"resumed-session-cache-touches-gated-by-setting","heading":"Prompt cache keepalive for resumed sessions","tier":"notice","area":"Prompt Cache","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/resumed-session-cache-touches-gated-by-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Prompt cache keepalive for resumed sessions\n\nResumed sessions can keep the 1-hour prompt cache warm on a timer, but only when server config sets resumeTouches\n\n**Unclear.** It is not clear where `resumeTouches` is set or whether you can change it yourself.\n\n**What**\n\nThe prompt cache lets the API reuse earlier parts of a conversation so replies come back faster and cost less. Claude Code can keep that cache warm by touching it on a timer. A resumed session is an earlier conversation you have reopened.\n\n- New code keeps the 1-hour prompt cache warm for resumed sessions by touching it on a timer.\n\n- It applies only to subscribers with a 1-hour cache lifetime, and only when server config sets `resumeTouches`.\n\n- Without `resumeTouches`, the keepalive stops for resumed sessions with the reason `resume_touches_off`. Before, there was no special check for resumed sessions.\n\n**Why**\n\nWhen it is enabled, a resumed conversation is less likely to lose its cache, which could mean fewer cache misses after you come back to it. When it is not enabled, resumed sessions do not keep the cache warm this way.\n\n- Area: Prompt Cache\n- Names: `resumeTouches`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}