ClaudeMemory
Long-term memory for Claude Code - automatic, intelligent, zero-configuration
What It Does
ClaudeMemory gives Claude Code a persistent memory across all your conversations. It automatically:
- ✅ Extracts durable facts from conversations (tech stack, preferences, decisions)
- ✅ Remembers project-specific and global knowledge
- ✅ Provides instant recall without manual prompting
- ✅ Maintains truth (handles conflicts, supersession)
No API keys. No configuration. Just works.
Quick Start
1. Install the Gem
gem install claude_memory
2. Install the Plugin
From within Claude Code, add the marketplace and install the plugin:
# Add the marketplace (one-time setup)
/plugin marketplace add codenamev/claude_memory
# Install the plugin
/plugin install claude-memory
3. Initialize Memory
Initialize both global and project-specific memory:
claude-memory init
This creates:
- Global database (
~/.claude/memory.sqlite3) - User-wide preferences - Project database (
.claude/memory.sqlite3) - Project-specific knowledge
4. Analyze Your Project (Optional)
Bootstrap memory with your project's tech stack:
/claude-memory:analyze
This reads your project files (Gemfile, package.json, etc.) and stores facts about languages, frameworks, tools, and conventions.
5. Verify Setup
claude-memory doctor
Use with Claude Code
Just talk naturally! Memory happens automatically.
You: "I'm building a Rails app with PostgreSQL, deploying to Heroku"
Claude: [helps with setup]
# Behind the scenes:
# - Session transcript ingested
# - Facts extracted automatically
# - No user action needed
Later:
You: "Help me add a background job"
Claude: "Based on my memory, you're using Rails with PostgreSQL..."
👉 See Getting Started Guide → 👉 View Example Conversations →
Why It Matters — Real A/B Test Results
We tested identical prompts with and without ClaudeMemory to measure the actual impact. Here's what we found:
Architecture Recall Without File Traversal
Prompt: "Explain the conflict detection and resolution system. Answer from knowledge only — do not read any files."
| Without Memory | With Memory | |
|---|---|---|
| Response | 16 lines: "I don't know this codebase — let me read the files" | 76 lines: correct 4-role PredicatePolicy explanation, resolution pipeline, specific examples |
| Outcome | Honest refusal — zero architectural understanding | Deep understanding without touching the filesystem |
Correct File Paths vs Hallucinated Guesses
Prompt: "I want to add a new predicate. Walk me through every file I need to update."
| Without Memory | With Memory | |
|---|---|---|
| Response | 6 steps targeting 3 non-existent files (predicate.rb, predicate_synonyms.rb, json_schema.rb) | 8 steps, all targeting real files with correct paths |
| Outcome | Plausible but wrong — would waste developer time | Actionable, correct, references actual commits |
Cross-Project Preferences
Prompt: "What are my standard development environment preferences across all my projects?"
| Without Memory | With Memory | |
|---|---|---|
| Response | "I don't have stored knowledge of your preferences" | Lists 7 real preferences: iTerm2, tmux, VS Code, PostgreSQL, Redis, Docker |
| Outcome | Blank slate every session | Personalized from day one |
When Memory Doesn't Help
File-searchable questions ("what version is this?") and one-shot code generation without explicit recall don't benefit — grep is equally effective. Memory shines when the answer isn't in any single file: architecture spanning dozens of classes, conventions from past sessions, decisions with rationale, and user preferences.
How It Works
- You chat with Claude - Tell it about your project
- Facts are extracted - Claude identifies durable knowledge
- Memory persists - Stored locally in SQLite
- Automatic recall - Claude remembers in future conversations