Skip to content

Releases: SimCubeLtd/mneme

Release list

v1.0.0

Choose a tag to compare

@prom3theu5 prom3theu5 released this 04 Jul 19:02
437a7c9

mneme v1.0.0 🌸

Git-based memory sync for Claude Code — pronounced NEE-mee.

First release. mneme keeps Claude Code's file-based memory in sync across your
machines through git — real history, real merges, nothing forgotten — instead
of a fragile cloud folder.

Claude Code stores per-project memory under ~/.claude/projects/<slug>/memory/,
which is local to one machine. mneme relocates that directory into a central git
repo, leaves a symlink in its place (Claude follows it transparently), and
reconciles machines with commitpull --rebasepush.

Highlights

  • Sync over git, not cloud sync. Every change is a commit. No online-only
    eviction, no MEMORY (1).md conflict copies, full revertible history.
  • Works across mismatched paths. Machines with different working-dir paths
    (/Users/you/… vs /home/you/… vs C:\…) still share memory, because each
    links into a shared bucket inside the repo rather than a path-keyed slug.
  • Auto-bucketing. The bucket name is derived from your project's git remote
    (…/my-project.gitmy-project), so it's identical on every clone with no
    configuration. Falls back to the folder name, then default.
  • Committable team config. setup writes a small .mneme.json at your
    project root recording the bucket + branch, so teammates who clone the codebase
    converge on the same shared memory without passing flags. The memory remote URL
    stays out of it by default (opt in with --shared-remote).
  • Multiple projects, one repo. Each project lives in its own bucket; one
    memory remote can hold them all. Use --repo to keep separate pools (e.g.
    work vs personal), persisted per-project.
  • Union merge for MEMORY.md. Two machines appending different facts merge
    cleanly — all lines from both sides are kept. Genuine edit collisions on other
    files halt loudly with a clear resolve/abort path (never silently lost).
  • Any git backend. GitHub, GitLab, self-hosted, or a bare repo on a USB
    stick / NAS via a file:// URL. Reuses your existing git auth.
  • Interactive kawaii dashboard. mneme dashboard (alias ui) — a full-screen
    TUI showing live link/repo/sync state, with s/p/l/r/q key actions.
  • Safe by design. Original memory is moved aside to *.old (never deleted);
    restore reverses setup and leaves the repo and its history untouched.

Commands

Command What it does
setup Relocate memory into the repo and symlink it. Idempotent.
sync Commit local memory, pull --rebase, then push. The everyday command.
push / pull Push without pulling / fetch-and-rebase without pushing.
remote Set or update the memory remote URL.
status Link state, repo cleanliness, ahead/behind the remote.
doctor Health checks — link integrity, stuck rebase, remote reachability.
restore Reverse setup: unlink, copy memory back. Never deletes the repo.
dashboard (ui) Interactive kawaii TUI.
version Print version and build info.

Install

Prebuilt binaries are attached below for macOS (arm64), Linux (x64), and
Windows (x64), each with a matching .sha256. The only runtime dependency is
git on your PATH.

# macOS (Apple Silicon)
curl -fsSL -o mneme \
  "https://github.com/SimCubeLtd/mneme/releases/download/v1.0.0/mneme-v1.0.0-macos-arm64"
chmod +x mneme && sudo mv mneme /usr/local/bin/
mneme version
# Linux (x64)
curl -fsSL -o mneme \
  "https://github.com/SimCubeLtd/mneme/releases/download/v1.0.0/mneme-v1.0.0-linux-x64"
chmod +x mneme && sudo mv mneme /usr/local/bin/

Windows (x64): download mneme-v1.0.0-windows-x64.exe, rename to mneme.exe,
and put it on your PATH.

Or build from source (Go 1.26+):

go install github.com/SimCubeLtd/mneme/cmd/mneme@latest

Quick start

# from the directory you launch Claude Code in:
mneme setup --remote-url git@github.com:you/claude-memory.git
mneme sync

Run setup once per machine, then sync whenever you want to reconcile. Wire
mneme sync into Claude Code's SessionStart / Stop hooks to sync
automatically.

Platform support

OS Link mechanism Status
macOS symlink First-class, tested
Linux symlink First-class, tested
Windows junction (mklink /J fallback) Experimental — junction path not yet verified on real Windows

Notes

  • Switch machines sequentially — don't run two live Claude sessions writing the
    same memory at once (that's what produces conflicts).
  • The name: Mneme (Μνήμη, "memory") was one of the three original Muses, the
    root of the word mnemonic — the art of not forgetting.