{"version":"2.1.221","anchor":"rewind-clears-tracked-file-state-for-the-removed-messages","canonical_anchor":"rewind-clears-tracked-file-state-for-the-removed-messages","heading":"Rewind clears tracked file state for the removed messages","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/rewind-clears-tracked-file-state-for-the-removed-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Rewind clears tracked file state for the removed messages\n\nAfter rewinding, Claude can read files again instead of complaining about stale read state.\n\n**What**\n\nRewinding a conversation no longer leaves stale read-file timestamps behind, so re-reading a file after a rewind is not blocked.\n\n**Details**\n\n- The sliced-off messages are scanned for read file paths and nested memory paths.\n- Those entries are dropped from the read-file tracking map and from the nested memory record.\n\n**Evidence**\n\n`nestedMemoryPaths`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}