{"version":"2.1.224","anchor":"session-lookup-can-match-a-project-by-the-directory-recorded","canonical_anchor":"session-lookup-can-match-a-project-by-the-directory-recorded","heading":"Session lookup can match a project by the directory recorded in its transcript","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/session-lookup-can-match-a-project-by-the-directory-recorded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Session lookup can match a project by the directory recorded in its transcript\n\nSessions in truncated or same-named project folders now resolve using the recorded working directory.\n\n**What**\n\nFinding the right project folder for a session no longer depends only on the folder name. Claude Code reads the working directory recorded inside the transcript files and compares it, optionally ignoring case, which disambiguates project folders whose names were truncated.\n\n**Details**\n\n- Reads a relocated path (\"relocated\" \/ \"relocatedCwd\") from the end of the file, falling back to \"cwd\" via a fast per-line scan of the head.\n- The recorded path is sanitised the same way project folder names are before comparison.\n- Transcript lookup by session id now also walks worktrees.\n\n**Evidence**\n\n`relocatedCwd`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}