claude-user-memory

claude-user-memory

A Claude Code plugin that gives Claude a persistent, cross-session memory layer about the user. Two isolated contexts — personal and work — so Claude can remember your preferences, role, ongoing projects, and corrections across sessions without mixing the two.

v2.0.0 is backend-agnostic. The plugin ships the contract (save / recall / commit-learnings skills + a personal/work routing rule) and leaves the concrete memory MCP to you. Pinecone, Mem0, or anything else — point the plugin at it via a workspace config file.

Claude Code's built-in per-project memory is great for code context, but it forgets everything about you the moment a new session starts, and it has no sense of which facts belong to your personal life vs. your professional work. This plugin fixes both — without locking you into a specific memory vendor.

What it does

Skill	When it fires	What it does
recall-user-memory	Claude is about to ask you something a returning collaborator would already know, or needs user-specific context to answer	Semantic search against the configured backend, then silently integrates the result
remember-user-fact	You state a preference, correct Claude, or share a durable fact	Atomic save to the configured backend, with duplicate-check before write
commit-learnings	End of session, handover, or "save what you learned"	Reviews the session, proposes candidate facts, shows them for approval, then batch-saves

All three skills share a deduction rule for picking the right context: default to personal; switch to work only on explicit override, work-repo cwd, or unambiguously business conversation. See CONTEXT.md for the full rule.

How context isolation works

The plugin requires that personal and work memory be physically separated at the backend — different indexes, different Mem0 projects, different accounts, whatever the backend supports. The routing rule in CONTEXT.md is a second layer of safety, not the only layer. Two separated stores means a personal fact cannot architecturally end up in the work store, regardless of what Claude decides in a given turn.

Installation

1. Install the plugin

claude plugins install danielrosehill/Claude-User-Memory-plugin

2. Stand up a memory backend and expose it as an MCP

Any backend works. Two recommended options:

• Pinecone — provision one index for personal, another for work (or a single index with two namespaces if you're comfortable with the extra discipline). Install the Pinecone MCP server and register it.
• Mem0 — create two projects in app.mem0.ai (one personal, one work). Configure two MCP HTTP servers pointed at https://mcp.mem0.ai/mcp and OAuth each separately.

Any other vector DB or memory service with an MCP interface is fair game.

3. Create .claude/memory-config.md in your workspace

The plugin reads this file to resolve save/recall to concrete MCP calls. Copy the template from the plugin (templates/memory-config.example.md) into your workspace's .claude/ directory and fill in:

• Your backend's MCP tool names for search / add / update
• Scope parameters to pass on every call (index/namespace for Pinecone; project_id/user_id for Mem0; etc.)
• How personal and work contexts are separated
• The record schema you want to commit to

Without this file, the skills will stop and ask you to create one — they will not guess a backend.

4. Restart Claude Code

The skills become active once the memory-config file is in place.

Usage

Mostly you don't invoke these skills directly — Claude will reach for them when the situation fits. Things that trigger them naturally:

• "Remember that I prefer X." → remember-user-fact
• "What's my preferred X?" → recall-user-memory
• "Save what you learned this session." → commit-learnings
• Any correction you give Claude ("don't do X, do Y") → remember-user-fact
• Any question where Claude would otherwise ask you something it should already know → recall-user-memory first

To force a context override, say "save this to work memory" or "check my personal memory".

Design notes