Feature Request
Cross-device memory sync for Claude Code
Problem
Claude Code stores memory files and session history locally in .claude/. Users who work across multiple machines (e.g. desktop and laptop) with the same account have completely separate memory and context on each device. This means:
- Feedback and preferences saved on one machine don't carry over
- Project context and user memories must be rebuilt from scratch on each device
- Conversations can't be continued across devices
- The experience feels fragmented for users who regularly switch machines
Proposed Solution
Sync Claude Code memory files across devices for the same authenticated user account. This could be:
- Cloud-synced memory — memory files sync via Anthropic's servers tied to the user's account
- Configurable sync path — let users specify a custom memory directory (e.g. a OneDrive/Dropbox/iCloud folder) in settings
- Session continuity — optionally allow resuming conversations started on another device
At minimum, a memory_path setting in settings.json that overrides the default local path would solve this elegantly and let users choose their own sync provider.
Current Workaround
Manual junction/symlink from the local memory folder to a cloud-synced directory. This works but is fragile (different usernames across machines means different project paths, and it requires manual setup per machine).
Environment
- Claude Code on Windows 11
- Multiple machines with same Anthropic account
Feature Request
Cross-device memory sync for Claude Code
Problem
Claude Code stores memory files and session history locally in
.claude/. Users who work across multiple machines (e.g. desktop and laptop) with the same account have completely separate memory and context on each device. This means:Proposed Solution
Sync Claude Code memory files across devices for the same authenticated user account. This could be:
At minimum, a
memory_pathsetting insettings.jsonthat overrides the default local path would solve this elegantly and let users choose their own sync provider.Current Workaround
Manual junction/symlink from the local memory folder to a cloud-synced directory. This works but is fragile (different usernames across machines means different project paths, and it requires manual setup per machine).
Environment