claude-code - 💡(How to fix) Fix [BUG] Windows junction/symlink project aliases create duplicate Claude Desktop projects and runtime-bound broken sessions [1 comments, 2 participants]

TL;DR

Resolving Windows junctions/symlinks before deriving the storage directory and updating the cwd string in memory may fix the issue.

Guidance

• Verify if the issue is caused by the literal cwd path string not being resolved to its actual path, leading to separate project instances and broken filesystem access.
• Check if updating the cwd string to resolve junctions/symlinks before deriving the storage directory resolves the issue.
• Consider implementing a mechanism to dynamically update the cwd string in memory when the junction is removed or changed.
• Test the application with different junction/symlink scenarios to ensure the fix covers all related failure modes.

Example

No code snippet is provided as the issue does not contain sufficient code details.

Notes

The provided information suggests a specific issue with Windows junctions/symlinks, but the exact implementation details are not available. The suggested fix is based on the assumption that resolving the junctions/symlinks before deriving the storage directory will resolve the issue.

Recommendation

Apply a workaround to resolve Windows junctions/symlinks before deriving the storage directory, as the root cause appears to be related to the literal cwd path string not being resolved.