Project memory files are not portable — stored outside project directory

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)