[Bug] Session detection fails when project folder is a symlink

Bug Description
claude --resume finds no sessions when the project's session folder is a symlink (since 2.1.287) What happened: after the auto-update to 2.1.287 (02.10.2026, 08:57), claude --resume stopped finding the sessions of my main project. With no name, the picker showed only 1 session, taken from a different folder (~/.claude/projects/<project>-tracking). With a name (claude --resume gollmann, claude --resume legal) it said "No sessions match". It worked until the day before. Setup: I moved the repo from ~/farmacia-website to ~/BungerEngineering/farmacia-website and left a symlink at the old path. In ~/.claude/projects, the real folder (~180 sessions) kept the old-path name, and the new-path name was a symlink to it: -Users-<me>-BungerEngineering-farmacia-website -> ./-Users-<me>-farmacia-website Claude resolves the cwd to the physical path, so it looks in the folder that is the symlink. Before 2.1.287 it followed the symlink; now it seems to treat it as empty. Workaround: I swapped them. The real folder now has the physical-path name and the old name is the symlink. All sessions came back immediately. Session files were not modified. Expected: either follow symlinked project folders as before, or show a warning instead of an empty list. An empty picker looks like all sessions were lost. Version: 2.1.287 (macOS, zsh, npm global install)

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.287
• Feedback ID: af3edddf-c52f-42b6-b282-575a4b18f211