memem

Persistent, self-evolving memory for Claude Code. Stop re-explaining your project every session.

For LLM/AI tool discovery, see llms.txt.

  ███╗   ███╗███████╗███╗   ███╗███████╗███╗   ███╗
  ████╗ ████║██╔════╝████╗ ████║██╔════╝████╗ ████║
  ██╔████╔██║█████╗  ██╔████╔██║█████╗  ██╔████╔██║
  ██║╚██╔╝██║██╔══╝  ██║╚██╔╝██║██╔══╝  ██║╚██╔╝██║
  ██║ ╚═╝ ██║███████╗██║ ╚═╝ ██║███████╗██║ ╚═╝ ██║
  ╚═╝     ╚═╝╚══════╝╚═╝     ╚═╝╚══════╝╚═╝     ╚═╝
  persistent memory for Claude Code

What is memem?

memem is a Claude Code plugin that gives Claude persistent memory across sessions. A background miner extracts durable lessons (decisions, conventions, bug fixes, preferences) from your completed sessions, stores them as markdown in an Obsidian vault, and automatically surfaces relevant ones at the start of each new session via a query-tailored briefing.

It's local-first: no cloud services, no API keys required, no vendor lock-in. Everything lives in ~/obsidian-brain/memem/memories/ as human-readable markdown.

When should I use memem?

Use memem if:

• You use Claude Code daily and keep re-explaining your project to every new session

• You want durable memory you can browse and edit as markdown

• You like local-first tools with zero vendor lock-in

• You already use Obsidian (memem plugs straight into your vault)

Skip memem if:

• CLAUDE.md works fine for you and you don't want a background daemon

• You need cloud-synced memory across machines (memem is local-only)

• You're on Python < 3.11

How is memem different from CLAUDE.md?

CLAUDE.md is a single hand-edited file per project. memem gives you:

• Automatic extraction — no manual note-taking, the miner captures lessons from every completed session

• Query-aware context — only the memories relevant to your current question get injected, not a static dump

• Self-evolving — memories merge, update, and deprecate automatically as your project evolves

• Cross-project — works across every Claude Code project you use, not scoped to one repo

• Security scanning — every write is scanned for prompt injection and credential exfiltration

• Browsable — Obsidian vault with graph view and backlinks for free

How do I install memem?

/plugin marketplace add TT-Wang/memem
/plugin install memem

That's it. On first run, bootstrap.sh self-heals everything:

1. Verifies Python ≥ 3.11

2. Installs uv if missing (via the official Astral installer)

3. Syncs deps into a plugin-local .venv (hash-cached against uv.lock)

4. Creates and canary-tests ~/.memem/ and ~/obsidian-brain/

5. Writes ~/.memem/.capabilities (used for degraded-mode decisions)

6. Execs the real MCP server

First run: ~5 seconds. Every run after: ~100ms. No separate pip install step.

What happens on my first Claude Code session?

You type your first message. The UserPromptSubmit hook fires and sees zero memories (you just installed it), so it injects a welcome banner into Claude's context. Claude reads the banner, tells you memem is active, and — if you have pre-existing Claude Code sessions — offers to mine them via /memem-mine-history.

You work normally. The miner daemon runs silently in the background. When your session ends and settles for 5 minutes, the miner extracts memories from the transcript using Claude Haiku and writes them to your vault.

Session 2 onwards: the hook sends your first message to context_assemble, which gives Haiku the relevant memories and asks it to synthesize a tailored briefing. You see a status banner like [memem] 12 memories · miner OK · assembly OK followed by the brief. Claude starts with full context — no re-explaining.

What does memem save?

It saves durable knowledge, not session logs:

• Architecture decisions with rationale ("we use RS256 JWTs because …")

• Conventions ("tests go in tests/ not spec/")

• Bug fixes you might forget ("bcrypt.compare is async — must await")

• User preferences ("prefer single commits, not stacked PRs")

• Known issues ("JWT_SECRET defaults to 'secret' if unset — tracked in #123")

It does NOT save:

• Raw session transcripts (those are searchable via transcript_search, not stored as memories)

• Trivial or obvious facts

• Session outcomes ("today I worked on X")

Where does memem store my memories?

You can point memem elsewhere via MEMEM_DIR and MEMEM_OBSIDIAN_VAULT env vars.

What are the MCP tools Claude can call?

What slash commands does memem add?

• /memem — welcome, status, help

• /memem-status — memory count, projects, search DB size, miner health

• /memem-doctor — preflight health check with fix instructions for any blocker

• /memem-mine — start the miner daemon manually (normally auto-starts)

• /memem-mine-history — opt-in: mine all your pre-install Claude Code sessions

What if the claude CLI isn't on my PATH?

memem enters degraded mode — it still works, just without Haiku-powered context assembly and smart recall. You get FTS-only keyword recall instead of query-tailored briefings. Every session shows [memem] N memories · miner OK · assembly degraded (claude CLI missing — FTS-only recall) at the top of the context, so you know why.

This is by design: missing optional dependencies should degrade, not fail.

How do I diagnose problems?

Run /memem-doctor. It runs the same preflight the bootstrap shim runs (Python version, mcp importable, claude CLI on PATH, directory writability, uv available), then prints a report labelled HEALTHY, DEGRADED, or FAILING with explicit fix instructions for each blocker.

For deeper debugging:

tail -f ~/.memem/bootstrap.log   # first-run shim log
tail -f ~/.memem/miner.log       # miner daemon log
cat ~/.memem/events.jsonl        # memory operation audit trail
python3 -m memem.server --status   # detailed status dump

How does the mining pipeline work?

Session ends → miner daemon sees the JSONL file in ~/.claude/projects/
  → Waits 5 minutes for the file to "settle" (no more writes)
  → Filters to human messages + assistant prose (strips tool calls, system reminders)
  → One Haiku call with the full context: "extract durable lessons"
  → Haiku returns JSON array of memory candidates
  → Each candidate runs: security scan → dedup check → contradiction detection → save
  → Index rebuilt, per-project playbooks grown and refined
  → Session marked COMPLETE in ~/.memem/.mined_sessions

How does the recall pipeline work?

First message in a new session → auto-recall.sh hook fires
  → Reads ~/.memem/.capabilities for status banner
  → If claude CLI is available → sends (message, memories) to Haiku
      → Haiku synthesizes a focused briefing (300-800 tokens usually)
      → Brief injected into Claude's context as "memem context briefing"
  → If claude CLI is missing → falls back to FTS-only keyword recall
  → Either way, Claude starts its reply with relevant context already loaded

Architecture

memem is split into small, focused modules:

• models.py — data types, path constants

• security.py — prompt injection + credential exfil scanning

• telemetry.py — access tracking, event log (atomic writes, fcntl-locked)

• search_index.py — SQLite FTS5 index

• obsidian_store.py — memory I/O, dedup scoring, contradiction detection

• playbook.py — per-project playbook grow + refine

• assembly.py — context assembly via Haiku

• capabilities.py — runtime feature detection for degraded mode

• storage.py — server-lifecycle helpers (PID management, miner auto-start)

• server.py — thin MCP entrypoint (FastMCP imported lazily)

• cli.py — command dispatcher for non-MCP entrypoints

• mining.py — session mining pipeline

Multi-signal recall scoring:

• 50% FTS relevance

• 15% recency (0.995^hours decay)

• 15% access history (usage reinforcement)

• 20% importance (1-5 scale from Haiku)

Memory schema (markdown frontmatter):

---
id: uuid
schema_version: 1
title: "descriptive title"
project: project-name
tags: [mined, project-name]
related: [id1, id2, id3]
created: 2026-04-13
updated: 2026-04-13
source_type: mined | user | import
source_session: abc12345
importance: 1-5
status: active | deprecated
valid_to:                     # set when deprecated
contradicts: [id1]            # flagged conflicts
---

Configuration

Setup Obsidian (optional, recommended)

memem works without Obsidian — it just writes markdown. But Obsidian gives you graph view and backlinks for free:

1. Download: https://obsidian.md (free)

2. Open ~/obsidian-brain as a vault

3. Memories appear in memem/memories/, playbooks in memem/playbooks/

4. Use Graph View to see how memories link via the related field

Requirements

• Claude Code

• Python ≥ 3.11

• uv (auto-installed by bootstrap.sh on first run)

• claude CLI on PATH (optional — required for Haiku-powered assembly; degraded mode works without it)

Development

git clone https://github.com/TT-Wang/memem.git
cd memem
pip install -e ".[dev]"
pytest             # 54 tests
ruff check .       # lint
mypy memem # type check (strict)

See CONTRIBUTING.md for the PR process and CHANGELOG.md for version history.

License

MIT