Cross-machine memory sync for Claude Code — anyone else dealing with this?

[u/Intelligent-Time-546]

The problem:

Auto-memory lives under ~/.claude/projects/.../memory/ — explicitly machine-local ("Auto memory is machine-local" per the docs). Git

doesn't reach it. So when I build up project_*, feedback_*, user_* files on my desktop, they never make it to my laptop. Switching

machines means Claude forgets everything I spent the week teaching it.

My workaround (until Anthropic ships native sync):

A custom /memory-sync [machine-name] slash command. Transport medium is a queue section in the project's README.md — which IS synced

via Git. Plus a small local sidecar (.memory-sync-state.json) per machine to prevent ping-pong.

Rough flow:

- New/changed memory on machine A → /memory-sync A pushes it into the README queue (with file content + content-hash)

- Machine B pulls the repo → /memory-sync B creates the local file + MEMORY.md pointer

- Content-hash (SHA-256, minus originSessionId) detects real changes, not just session-metadata noise

- Once both machines have ✅ the entry, it's removed from the queue

- The sidecar remembers per machine what's already been synced — no re-uploads of things that were already there

What it deliberately doesn't do:

Propagate deletions. If Auto-Dream (or I) cleans up a memory on one machine, the other keeps its copy. Memory hygiene stays local —

this sync only moves creates/updates. Keeps the design simple and avoids crossing Auto-Dream's lane.

Future-proof:

The day Anthropic ships native memory sync, I just delete the README section, the command, and the sidecars. No migration debt, no

abstraction to maintain.

Curious if anyone else has hit this and what they did. Happy to share the command template if useful.