{"version":"2.1.281","anchor":"clearing-session-caches-now-also-clears-webfetchhistory","canonical_anchor":"clearing-session-caches-now-also-clears-webfetchhistory","heading":"Clearing session caches now also clears WebFetchHistory","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/clearing-session-caches-now-also-clears-webfetchhistory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Clearing session caches now also clears WebFetchHistory\n\nClearing session caches now also clears WebFetchHistory alongside WebFetchCache and ToolSearchDescriptionCache\n\n**Unclear.** The finding does not say what `WebFetchHistory` holds or when the cache-clear routine runs.\n\n**What**\n\nClaude Code keeps some stored data during a session, called caches, so it does not have to repeat work. The routine that clears these caches now also clears one called `WebFetchHistory`, in addition to `WebFetchCache` and `ToolSearchDescriptionCache` which it already cleared.\n\n**Why**\n\nWhen the caches are cleared, web fetch history no longer carries over while the other caches are reset.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}