{"version":"2.1.290","anchor":"history-prefetch-spool-hardened-with-digest-check","canonical_anchor":"history-prefetch-spool-hardened-with-digest-check","heading":"Temporary files for fetched session history are now checked for tampering","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/history-prefetch-spool-hardened-with-digest-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Temporary files for fetched session history are now checked for tampering\n\nFetched session history is now saved in a private temporary folder and checked for changes before it is read\n\n**What**\n\nWhen Claude Code fetches the history of a remote session, it saves it in temporary files before reading it back. Those files now get more protection:\n\n- They go in a private temporary folder whose name starts with `cc-history-prefetch-`.\n\n- Each file is created fresh, and creation fails if the file already exists.\n\n- A fingerprint of the content is taken while writing and checked again when reading.\n\nIf the fingerprint does not match, Claude Code skips that file. Before, it read the file without any check.\n\n**Why**\n\nAnother program on the same machine can no longer quietly change these files between writing and reading.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}