By ErebusEnigma
Persistent, searchable context storage across Claude Code sessions using SQLite + FTS5
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Persistent, searchable context storage across Claude Code sessions using SQLite + FTS5.
Claude Code sessions are ephemeral - every conversation starts from zero. Close the terminal and everything you discussed, decided, and solved is gone. The only way to get that context back is to re-explain it or hope Claude reads the right files.
context-memory fixes this.
/recall authentication pulls up exactly what you did, what you decided, and why./recall retry pattern --detailed brings it back./recall --project scopes to whatever you're working in. Instant refresher on where you left off./recall CORS finds it regardless of which project it came from./remember and Claude does the rest: summarizes, extracts topics, identifies key code, stores it all. Add a note if you want, or don't.Without it, every session is a blank slate. With it, Claude Code has a long-term memory that grows more valuable the more you use it.
Core:
/remember generates rich summaries with brief/detailed text, key decisions, problems solved, technologies used, and outcome classification (success/partial/abandoned)Hooks:
/recall feature/auth-refactor finds sessions from that branchcontext_load_checkpoint MCP tool/remember save in the same project within a configurable window (default 5 minutes) and skips if one existsstop_hook_active to prevent recursive hook invocationExtras:
db_save.py, db_search.py, db_prune.py, db_init.py) have full argparse CLIs with --helpnpx claudepluginhub erebusenigma/context-memoryDAG-based lossless context management for Claude Code. Every message from every session is persisted in a SQLite vault with FTS5 search. Summaries form a directed acyclic graph - nothing is ever lost.
Persistent local memory for Claude Code. Every tool call, every file edit, every thinking block from every session — stored verbatim on your machine. Semantic recall in ~126ms with zero API calls.
Persistent memory for Claude Code. Capture work across sessions and recall relevant context.
Automatic semantic memory for Claude Code — remembers what you worked on across sessions
Persistent memory across Claude Code sessions using Cognis
Persistent memory system for Claude Code with SQLite, FTS5, and vector search