Codenamev Claude Memory
- 23 repo stars
- Updated July 16, 2026
- codenamev/claude_memory
codenamev-claude_memory is a Claude Code plugin that provides journey-wide, SQLite-backed long-term memory via hooks and MCP tools.
About
codenamev-claude_memory is a Claude Code plugin that adds long-term, self-managed memory through hooks, MCP tools, and SQLite so developers do not restart context from zero every session. It targets developers who treat the coding agent as a long-running collaborator on one product: decisions, constraints, and facts should persist with provenance instead of living only in yesterday’s chat export. Hooks automate when memory is written or refreshed; MCP exposes structured operations the agent can call; SQLite keeps data local and under your control. Expect to invest setup time in maintenance and extraction behavior—the listing stresses truth and tracking, which implies you still curate what gets remembered. Install during Build when you wire agent infrastructure, then rely on it across Idea research recall, shipping fixes, and Operate iteration without re-explaining your stack each time.
- Long-term, self-managed memory layer for Claude Code beyond a single chat thread
- Hooks and MCP tools coordinate capture, extraction, and maintenance workflows
- SQLite-backed local store with provenance and truth-oriented tracking keywords
- Designed for ongoing memory upkeep rather than manual copy-paste session notes
- Single-plugin marketplace entry focused on memory—not a general skill library
Codenamev Claude Memory by the numbers
- Data as of Jul 24, 2026 (Skillselion catalog sync)
/plugin install codenamev-claude_memory@codenamev/claude_memoryAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 23 |
|---|---|
| Last updated | July 16, 2026 |
| Repository | codenamev/claude_memory ↗ |
What it does
Give Claude Code durable, self-managed memory across sessions using hooks, MCP tools, and a local SQLite store with provenance tracking.
Who is it for?
Best when you're on long-horizon products and want local, hook-driven memory instead of cloud-only chat history.
Skip if: Skip if you need multi-user shared knowledge bases with enterprise ACLs and no local SQLite maintenance.
What you get
After setup, important facts and provenance can persist in a self-managed local memory store the agent can read and maintain across sessions.
- Persistent memory store the agent can query across sessions
- Hook-driven capture and maintenance of project-relevant facts
- Provenance-oriented tracking for what the agent treats as true
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
Persistent agent memory system with hooks and MCP, not a brainstorming or planning-only skill.
FAQ
Who is Codenamev Claude Memory for?
Developers using Claude Code on multi-week projects who need durable, locally controlled memory with extraction and provenance—not ephemeral thread context.
When should I use Codenamev Claude Memory?
Use it as soon as agent setup begins and keep it on across the journey whenever session continuity, tracked facts, or memory maintenance matter.
How do I add Codenamev Claude Memory to my agent?
Install the codenamev/claude_memory plugin marketplace entry in Claude Code, configure hooks and the MCP memory server, and ensure SQLite storage paths are writable on your machine.