Guide

Share Claude Code memory with your team

Every developer's Claude Code learns the same things about a codebase separately: which test command is the real one, which service must never be restarted on a Friday, the fix that worked last time. That auto memory stays on the machine that wrote it (Claude Code docs, memory), so a new teammate's agent starts from nothing and every agent repeats the same mistakes.

memgit gives the team one memory store. Each teammate's agent reads it at session start and writes to it as it learns, and every change is a checkpoint you can diff and roll back.

The person setting it up

pip install memgit
memgit init
memgit cloud signup
memgit cloud team create backend
memgit cloud link backend/memory
memgit cloud team invite backend

memgit init creates the store and imports the memory Claude Code already has. memgit cloud signup creates the account and turns sync on. team create makes the team, link puts this store in it, and team invite prints an invite link. The secret that unlocks the team sits in the part of the link after the #, which browsers and servers never send, so memgit cloud never sees it. By default a link works for 10 people and 14 days; change that with --uses and --days.

Each teammate

pip install memgit
memgit init
memgit cloud signup
memgit cloud team join "<the invite link>"
memgit cloud link backend/memory

After that, the teammate's next Claude Code session opens with what the rest of the team's agents have learned, and what it saves reaches everyone else on its own. Inside Claude Code, the plugin replaces the first two lines:

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

When an agent writes something wrong

memgit log -n 5
memgit diff <checkpoint>
memgit rollback <checkpoint>

A shared memory needs an undo. log shows who changed what, diff shows the exact change, and rollback restores the earlier version while keeping the history. The undo guide walks through it.

What the server can see

Nothing readable. Each member holds the team key sealed to their own keys, derived on their machine from their passphrase. Memories are encrypted before they leave a machine, and the server stores ciphertext. The design is on the security page.

Cost

The local CLI is free and MIT licensed. Sync is memgit Pro, per person: each account gets 14 days free with no card, and the owner's 14 days start when the first teammate joins. After that it is $12 a month or $99 a year per account. If a plan lapses, every memory stays on each machine, readable and exportable.