memesh

🌐 English | 繁體中文 | 简体中文 | 日本語 | 한국어 | Português | Français | Deutsch | Tiếng Việt | Español | ภาษาไทย

MeMesh LLM Memory

Local memory for Claude Code and MCP coding agents.
One SQLite file. No Docker. No cloud required.

---

The Problem

Your coding agent forgets what happened between sessions. Every architecture decision, bug fix, failed test, and hard-won lesson has to be re-explained. Claude Code starts fresh, re-discovers old constraints, and burns context on things it should already know.

MeMesh gives coding agents persistent, searchable, evolving local memory.

This package is the local memory layer of the MeMesh product family. It is intentionally small and open-source: install it with npm, keep your memory in ~/.memesh/knowledge-graph.db, and connect it to Claude Code or any MCP-compatible client. Hosted workspace and enterprise operating-system products should stay separate from this package's README and roadmap.

---

Proof — 95.40% R@5 on LongMemEval-S

MeMesh's retrieval engine is FTS5 alone (no LLM, no embeddings on the hot path), measured against the public LongMemEval-S benchmark (500 questions, MIT-licensed):

System	R@5	Source
MeMesh (Mode A, FTS5)	95.40%	benchmarks/longmemeval/RESULTS.md
MemPalace	96.6%	Vendor self-report
Supermemory	~82%	Vendor estimate
Zep	63.8%	LongMemEval paper
Mem0	49.0%	LongMemEval paper

Reproduction commands, dataset SHA256, raw per-question results, and known-failure analysis are all in benchmarks/longmemeval/. Re-runnable in ~10 seconds.

---

Get Started in 60 Seconds

Option A — Claude Code plugin (one-line install)

If you use Claude Code, install MeMesh as a plugin from inside the CLI:

/plugin marketplace add PCIRCLE-AI/memesh-llm-memory
/plugin install memesh@pcircle-memesh

Claude Code wires hooks, skills, and the MCP server automatically. You get in-session auto-capture, proactive recall, the /memesh skill (remember / recall / learn / forget) inside the Claude Code conversation, and remember / recall / forget / learn available as MCP tools to the agent. The CLI and the local dashboard are also fully accessible without any extra global install — npx @pcircle/memesh <command> runs every CLI command, and npx @pcircle/memesh launches the dashboard at localhost:3737. The MCP server uses the same npx-based launch pattern as Anthropic's official plugins (e.g. context7), so no npm install -g is needed for any feature.

Option B — npm global (optional optimisation)

If you want the binary directly on your shell PATH (so plain memesh, memesh-mcp, etc. work in any terminal without the per-call npx lookup), or you want to expose memesh-mcp as a fixed-path stdio command to non-Claude-Code MCP clients (Cursor, Cline, terminal-only flows):

npm install -g @pcircle/memesh

First-install notes (one-time):

• Native modules — better-sqlite3 and sqlite-vec install via prebuilt binaries on macOS (arm64/x64), Linux (x64/arm64), and Windows x64. On uncommon platforms or when prebuilds fail, you'll need a working C/C++ toolchain.
• Embedding model — the first call that triggers a local embedding (e.g. recall with semantic mode) downloads Xenova/all-MiniLM-L6-v2 (~80 MB) into ~/.memesh/models/. Subsequent calls are instant. The default retrieval path (FTS5) does not require this download.

Step 1.5: Wire MeMesh into Claude Code (npm path only)

If you installed via Option A (/plugin install memesh@pcircle-memesh), skip this step — Claude Code wires plugin hooks automatically.

If you installed via Option B (npm install -g), the CLI is on your PATH and the MCP server is registered, but the Claude Code session hooks are not auto-wired. Without them you can still use memesh remember / recall manually, but the auto-capture loop (sessions → lessons → recall on next session) is silent.