{"version":"2.1.307","anchor":"cache-reuse-check-the-one-hour-requirement-is-replaced-by-a","canonical_anchor":"cache-reuse-check-the-one-hour-requirement-is-replaced-by-a","heading":"Reusing the cache before compaction no longer needs a one-hour cache","tier":"notice","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/cache-reuse-check-the-one-hour-requirement-is-replaced-by-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Reusing the cache before compaction no longer needs a one-hour cache\n\nThe check for reusing cached conversation before compaction no longer requires a one-hour cache lifetime and still stops when the cache has lapsed\n\n**Unclear.** It is not clear what the earlier-computed reason checks, so whether reuse now happens with shorter cache lifetimes is unsettled.\n\n**What**\n\nCompaction is when Claude Code summarises a long conversation to free up room. Before it does that, it checks whether it can reuse the prompt cache, a stored copy of the earlier conversation that can be reused instead of being sent and processed again.\n\nThat check has changed:\n\n- The one-hour requirement is gone. Previously the check refused reuse unless the cache was set to last one hour.\n\n- A reason worked out earlier is now used instead. If an earlier step found a reason not to reuse the cache, that reason is returned.\n\n- A lapsed cache still blocks reuse.\n\n**Why**\n\nIn practice, the faster path that reuses the cache before compaction may now be taken in more situations than before, including when the cache is not set to last one hour.\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}