Claude Code hook

Claude Memory

Long-term, self-managed memory for Claude Code using hooks, MCP tools, and SQLite

27 stars 2 forksHooks Plugin marketplace Source

Install

Inside Claude Code
/plugin marketplace add codenamev/claude_memory

Found in the project README. Check it for setup steps after installing.

From source
git clone https://github.com/codenamev/claude_memory.git

From the README

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)
- ✅ Tracks *what happened*, not just *what's true* — an episodic observation log alongside the facts (0.13.0+)
- ✅ Promotes an observation to a fact only after it recurs — a corroboration gate against one-off noise

No API keys. No configuration. Just works.

ClaudeMemory now has two complementary halves: a *semantic* fact store ("what is true" — your stack, conventions, decisions) and an *episodic* observation layer ("what happened" — the narrative of your sessions). Observations are deduplicated and consolidated automatically, and only graduate to facts once corroborated — so fleeting mentions never harden into false memory. See Episodic Memory.

Quick Start

1. Install the Gem

2. Install the Plugin

From within Claude Code, add the marketplace and install the plugin:

3. Initialize Memory

Initialize both global and project-specific memory:

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:

This reads your project files (Gemfile, package.json, etc.) and stores facts about languages, frameworks, tools, and conventions.

5. Verify Setup

Use with Claude Code
Just talk naturally! Memory happens automatically.

Later:

👉 See Getting…
Read the full README on GitHub

How hooks work

  • Hooks are shell commands Claude Code runs at fixed points: before or after a tool call, when you submit a prompt, when Claude stops, on notifications and at session start.
  • They are set in the hooks section of ~/.claude/settings.json (or .claude/settings.json for a project), or come bundled in a plugin.
  • A hook can block a tool call, add context, or run a formatter or test. Read the scripts before you install them: they run on your machine with your permissions.
Claude Code docs

Details

Type
Hooks
Language
Ruby
License
MIT
Last updated
14 October 2026

FAQ

What is Claude Memory?

Long-term, self-managed memory for Claude Code using hooks, MCP tools, and SQLite It is a hook for Claude Code, from codenamev/claude_memory on GitHub.

How do I install Claude Memory?

Run /plugin marketplace add codenamev/claude_memory inside Claude Code, then follow the setup in the README.

Is Claude Memory popular?

codenamev/claude_memory has 27 GitHub stars and 2 forks. It was last updated on 14 October 2026.

More hooks

Browse the most popular Claude Code mods, all hooks, or the skills and MCP server directories.