Claude Mem Sync

claude-mem-sync
Team memory sharing for claude-mem — sync AI memories across developers via git.

Official documentation

Table of Contents

- Why This Exists
- What It Does
- Step-by-Step Setup Guide
  - Step 1: Install Prerequisites
  - Step 2: Install the Claude Code Plugin
  - Step 3: Run the Setup Wizard
  - Step 4: Create the Shared Team Repository
  - Step 5: Set Up GitHub Actions (CI/CD)
  - Step 6: Your First Export
  - Step 7: Import Team Memories
  - Step 8: Enable Developer Profiles
  - Step 9: Enable Knowledge Distillation (optional)
  - Step 10: Launch the Dashboard
  - Step 11: Set Up Automatic Scheduling (optional)
- Configuration Reference
- CLI Reference
- Web Dashboard
- Developer Knowledge Profiles
- Knowledge Distillation
- Eviction & Scoring
- Destination Patterns
- Maintenance
- Security & Privacy
- Architecture
- Publishing a Release (maintainers)
- Troubleshooting
- License

Why This Exists

claude-mem gives Claude persistent memory across sessions, storing observations (decisions, bugfixes, discoveries) in a local SQLite database. But it's designed for single-user, per-machine usage.

When a team works on the same project:

- Each developer has their own isolated memory database
- Developer A discovers a critical pattern — developers B through L never learn about it
- The same bugs get rediscovered, the same decisions re-debated
- There is no native team mode, no shared database, no automatic sync

claude-mem-sync bridges this gap with filtered, scored, deduplicated team memory sharing using git as the transport layer.

What It Does

Features:

- Filtered export — only share what matters (by type, keyword, or tag)
- Intelligent eviction — scoring system prevents unbounded DB growth
- Deduplication — composite key dedup across developers
-…