Project memory files are not portable — stored outside project directory

[fgartland4]

Problem

Claude Code stores project memory files in a hardcoded local path (~/.claude/projects/) that is:

1. Outside the project directory — even when the project lives on a cloud-synced drive (OneDrive, Dropbox, etc.), memory files are stored locally and do not sync
2. Not version-controlled — memory files are not in the git repo, so they're not on GitHub or any backup
3. Not portable across machines — switching computers means losing all project memory
4. Hidden — the .claude folder in the user profile is not visible by default in Windows Explorer, so users don't even know where these files are

Impact

I have spent four intensive collaboration sessions building up 29 memory files that represent the strategic foundation of my project — collaboration preferences, design decisions, domain knowledge, architectural context. This is hours of carefully constructed context that enables Claude to pick up where the last session left off.

I am switching computers in a few days. None of this will transfer. I had no idea these files were stored outside my project directory until discovering it by accident today.

Expected Behavior

Project memory files should either:

• Live inside the project directory (e.g., .claude/memory/ within the repo) so they travel with the project
• Or provide a configurable path so users can choose where memory is stored
• At minimum, users should be clearly informed where memory files are stored and warned about portability

Environment

• Windows 11 Enterprise
• Claude Code CLI
• Project directory on OneDrive (C:\Users\...\OneDrive - Skillable\Claude-Code)
• Memory stored at C:\Users\...\.claude\projects\C--Users-...\memory\ (local only)

[github-actions]

Found 3 possible duplicate issues:

1. Move project memory to .claude/memory/ inside the project #42198
2. Feature Request: Allow project-scoped memory to be stored inside the repository for cross-device sync #38519
3. Allow configurable memory storage path #41532

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #42198.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[iLeonelPerea]

This is exactly the problem. My workaround: add an explicit rule in CLAUDE.md that tells Claude to write all memory files to a memory/ folder inside the project root, then sync the project via Syncthing (LAN-only). Memory becomes portable because it lives where the code lives.

Writeup: https://alebrije.io/blog/never-re-explain-sync-claude-memory-mac-windows/

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.