{"version":"2.1.251","anchor":"moving-a-session-transcript-no-longer-overwrites-what-is-alr","canonical_anchor":"moving-a-session-transcript-no-longer-overwrites-what-is-alr","heading":"Moving a session transcript no longer overwrites what is already there","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/moving-a-session-transcript-no-longer-overwrites-what-is-alr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Moving a session transcript no longer overwrites what is already there\n\nMoving a session transcript now sets aside any existing file instead of destroying it.\n\n**What**\n\nWhen a session transcript is relocated to a new project path and something already occupies the destination, the existing file is renamed aside with a timestamped \"superseded\" suffix rather than deleted, and it is put back if the move then fails.\n\n**Details**\n\n- Applies to every transcript relocation.\n\n**Evidence**\n\n`existing destination set aside at`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}