{"version":"2.1.323","anchor":"session-return-to-directory-message-covers-a-launch-folder-f","canonical_anchor":"session-return-to-directory-message-covers-a-launch-folder-f","heading":"Resumed sessions can return to a launch folder when the original is gone","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/session-return-to-directory-message-covers-a-launch-folder-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Resumed sessions can return to a launch folder when the original is gone\n\nIf a session's original folder no longer exists, Claude Code can put it back in a folder it was launched with and says so\n\n**What**\n\nWhen you return to a session whose original folder has been removed, Claude Code can now place it in one of the folders the session was launched with. A message tells you this happened.\n\nBefore, there were only two messages here: one saying the original folder was missing, and one for falling back to a worktree, which is a separate working copy of a git project.\n\n**Why**\n\nIf a session reopens somewhere you did not expect, the message tells you why.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}