By memvid
Persist Claude Code's memory across sessions by storing discoveries, decisions, and solutions in a portable .mv2 file. Search, query, and recall past context to maintain continuity in your work.
https://github.com/user-attachments/assets/b57cb3db-576b-4c1f-af92-95796ba3fb5b
You: "Remember that auth bug we fixed?"
Claude: "I don't have memory of previous conversations."
You: "We spent 3 hours on it yesterday"
Claude: "I'd be happy to help debug from scratch!"
200K context window. Zero memory between sessions.
You're paying for a goldfish with a PhD.
You: "What did we decide about auth?"
Claude: "We chose JWT over sessions for your microservices.
The refresh token issue - here's exactly what we fixed..."
One file. Claude remembers everything.
# One-time setup (if you haven't used GitHub plugins before)
git config --global url."https://github.com/".insteadOf "[email protected]:"
# In Claude Code
/plugin add marketplace memvid/claude-brain
Then: /plugins → Installed → mind Enable Plugin → Restart.
Done.
After install, Claude's memory lives in one file:
your-project/
└── .claude/
└── mind.mv2 # Claude's brain. That's it.
No database. No cloud. No API keys.
What gets captured:
Why one file?
git commit → version control Claude's brainscp → transfer anywhereIn Claude Code:
/mind stats # memory statistics
/mind search "authentication" # find past context
/mind ask "why did we choose X?" # ask your memory
/mind recent # what happened lately
Or just ask naturally: "mind stats", "search my memory for auth bugs", etc.
For power users who want direct access to their memory file:
npm install -g memvid-cli
memvid stats .claude/mind.mv2 # view memory stats
memvid find .claude/mind.mv2 "auth" # search memories
memvid ask .claude/mind.mv2 "why JWT?" # ask questions
memvid timeline .claude/mind.mv2 # view timeline
Empty: ~70KB. Grows ~1KB per memory. A year of use stays under 5MB.
100% local. Nothing leaves your machine. Ever.
Sub-millisecond. Native Rust core. Searches 10K+ memories in <1ms.
rm .claude/mind.mv2
Built on memvid - the single-file memory engine
If this saved you time, star the repo
Send me your .mv2 file and I'll tell you what's wrong with your code. No context needed - I already know everything.
Matches all tools
Hooks run on every tool call, not just specific ones
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.
npx claudepluginhub memvid/memvid-mind --plugin mindPersistent local memory for Claude Code. Cross-session recall with vector search, automatic archiving, zero cloud dependencies.
Persistent memory across Claude Code sessions using Cognis
Persistent memory for Claude Code. Capture work across sessions and recall relevant context.
Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF search with episode batching. Single SQLite DB, no external services. A lighter, lower-cost alternative to claude-mem (episode batching + a smaller model; cost savings are an internal estimate, not a measured benchmark).
Persistent memory system for Claude Code - seamlessly preserve context across sessions
Persistent memory system for Claude Code with enforced context