{"version":"2.1.317","anchor":"prompt-cache-ttl-1h-upgrade-ask-recorded-for-resumed-sessio","canonical_anchor":"prompt-cache-ttl-1h-upgrade-ask-recorded-for-resumed-sessio","heading":"Resumed sessions may ask for a longer prompt cache","tier":"internal","area":"Prompt Cache","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/prompt-cache-ttl-1h-upgrade-ask-recorded-for-resumed-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Resumed sessions may ask for a longer prompt cache\n\nWhen you resume a session whose last reply used a 5-minute prompt cache, Claude Code may record a request for a 1-hour cache\n\n**Unclear.** What the recorded 1-hour request changes for a resumed session is not clear.\n\n**What**\n\nThe prompt cache keeps recent conversation content on the server so it does not have to be processed again. It can last 5 minutes or 1 hour. When you resume a session and the last reply used the 5-minute cache, Claude Code may now record a request to move to the 1-hour cache. It does this only when all of these hold:\n\n- a model is known for the session\n\n- the saved entry did not come from a remote source\n\n- the session was not forked from another one\n\n- a 1-hour cache is available\n\n**Why**\n\nThis concerns how long cached content lasts when you pick a session back up.\n\n- Area: Prompt Cache\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}