claude-code - 💡(How to fix) Fix Session memory should not be scoped to working directory path [1 comments, 2 participants]

TL;DR

Assign a named project ID to use as the memory key instead of the directory path to resolve memory orphaning issues.

Guidance

• Introduce a configurable project ID (e.g., in CLAUDE.md or a config flag) to serve as the memory key.
• Update the auto-memory system to use this project ID when storing memories, ensuring backwards compatibility by defaulting to the directory-derived key.
• Consider adding a migration mechanism to associate existing memories with their respective project IDs.
• Evaluate the impact of this change on existing workflows and session resumption.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The suggested fix assumes that implementing a project ID-based memory key will not introduce significant performance or complexity issues. Further analysis may be required to ensure a seamless integration with the existing auto-memory system.

Recommendation

Apply the workaround by introducing a configurable project ID, as it directly addresses the issue of memory orphaning and provides a flexible solution for users to manage their sessions across different workspaces and directory changes.