SkillsApr 9, 2026·3 min read

Claude Memory Compiler — Evolving Knowledge Base

Auto-capture Claude Code sessions into a structured knowledge base. Hooks extract decisions and lessons, compiler organizes into cross-referenced articles. No vector DB needed. 365+ stars.

TL;DR
Auto-capture Claude Code sessions into structured, cross-referenced knowledge articles without a vector DB.
§01

What it is

Claude Memory Compiler automatically captures decisions, patterns, and lessons from your Claude Code sessions and compiles them into a structured knowledge base. Hooks run after each session to extract noteworthy information, and a compiler step organizes everything into cross-referenced articles. The result is an evolving wiki that grows as you work, without requiring a vector database or external infrastructure.

This tool targets developers who use Claude Code daily and want to build institutional memory from their AI-assisted coding sessions. Teams that lose context between sessions or across team members benefit most.

§02

How it saves time or tokens

Without persistent memory, developers re-explain context to Claude Code every session, wasting tokens on repetition. Claude Memory Compiler eliminates this by surfacing past decisions and patterns automatically. The structured output means you can reference previous solutions directly instead of re-deriving them, cutting both token consumption and debugging time.

§03

How to use

  1. Clone the repository and install dependencies
  2. Configure hooks to run after Claude Code sessions
  3. Run the compiler to organize captured knowledge into cross-referenced articles
§04

Example

git clone https://github.com/anthropics/claude-memory-compiler.git
cd claude-memory-compiler
npm install

# Configure hooks
npm run setup-hooks

# After working sessions, compile knowledge
npm run compile

# Browse your knowledge base
npm run serve
§05

Related on TokRepo

§06

Common pitfalls

  • The compiler works best with frequent, focused sessions rather than marathon coding sprints that mix unrelated topics
  • Knowledge articles need occasional manual curation to merge duplicates and correct misclassifications
  • Hook configuration must match your Claude Code setup; incorrect paths cause silent failures

Frequently Asked Questions

Does Claude Memory Compiler require a vector database?+

No. The system uses structured markdown articles with cross-references and full-text search. There is no dependency on a vector database, embedding model, or external search infrastructure.

How does it capture information from sessions?+

Hooks run after Claude Code sessions to extract decisions, patterns, and lessons from the conversation. The compiler then organizes these extractions into structured articles with cross-references to related topics.

Can multiple team members share a knowledge base?+

Yes. The knowledge base is stored as files that can be committed to a shared Git repository. Team members compile their sessions into the same base, building collective institutional memory.

How large does the knowledge base get over time?+

Growth depends on session frequency and content. The compiler deduplicates and merges related topics, so the knowledge base grows in depth rather than unbounded breadth. Periodic curation keeps it manageable.

Does it work with other AI coding tools besides Claude Code?+

The hooks are designed for Claude Code sessions. Adapting them to other tools requires modifying the extraction logic to match that tool's session format and output structure.

Citations (3)
🙏

Source & Thanks

Created by Cole Medin. Licensed under open source.

claude-memory-compiler — ⭐ 365+

Thanks to Cole Medin for building a practical memory system for Claude Code power users.

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets