Guide

Claude Code memory on every machine

Claude Code remembers what it learns about a project: build commands, conventions, fixes that worked. It keeps that auto memory under ~/.claude/projects/<project>/memory/, and its documentation says the memory is machine-local: the files are not shared across machines or cloud environments (Claude Code docs, memory). Open the same project on your desktop, a server or a teammate's laptop and Claude starts without it.

memgit keeps one memory store that every machine reads. This guide sets it up on two machines.

On the first machine

pip install memgit
memgit init
memgit cloud signup

memgit init creates the store and imports the memory Claude Code already has, so the store starts full. It also offers to connect the other AI tools it finds (Cursor, Codex, Gemini CLI) to the same store. memgit cloud signup asks for an email and a passphrase, creates the account and turns sync on. From then on every save is uploaded on its own.

Inside Claude Code you can install the plugin instead of the first two lines:

/plugin marketplace add code4161/claude-plugins
/plugin install memgit@memgit

On the second machine

pip install memgit
memgit init
memgit cloud login

memgit cloud login uses the same email and passphrase and links this store to the first one. The next Claude Code session on this machine pulls before it starts, so it opens with the memory the first machine built, and anything either machine saves reaches the other.

What the server can see

Nothing readable. Your keys are derived on your machine from the passphrase, and every memory is encrypted before it leaves. The server stores ciphertext, which is also why a lost passphrase cannot be recovered. The design is on the security page.

Cost

The local CLI is free and MIT licensed. Sync is memgit Pro: 14 days free with no card, then $12 a month or $99 a year. If you stop paying, sync stops and every memory stays on each machine, readable and exportable.

Check it worked

memgit cloud whoami
memgit log -n 3

whoami shows the account and the linked store; log on the second machine shows the checkpoints the first machine made.