{"version":"2.1.314","anchor":"session-transcript-file-existence-now-re-probed-tracking-no","canonical_anchor":"session-transcript-file-existence-now-re-probed-tracking-no","heading":"Claude Code now checks a session file still exists before reusing its location","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/session-transcript-file-existence-now-re-probed-tracking-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Claude Code now checks a session file still exists before reusing its location\n\nWhen looking up a session's file, Claude Code now checks the disk again and treats a missing file as gone, unless it has not been written yet\n\n**What**\n\nEach session is saved as a transcript file on disk. When Claude Code looks up a session's file, it now checks the disk again instead of trusting the location it remembered. If the file has disappeared, the lookup reports that there is no file. A session that has only just started and has not written its file yet is remembered as such, so it is not treated as missing.\n\n**Why**\n\nIf a transcript file is moved or deleted, Claude Code should no longer try to resume from a location that no longer exists.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}