claude-brain
From public sourcesGive Claude Code photographic memory in ONE portable file. No database, no SQLite, no ChromaDB - just a single .mv2 file you can git commit, scp, or share. Native Rust core with sub-ms operations.
Overview
- ai-tools
- anthropic
- claude
- claude-agents
- claude-ai
- claude-code
- claude-skills
- context-window
- developer-tools
- llm-memory
- long-term-memory
- memvid
Installation
Commands are shown, never run by the marketplace. Check them against the official documentation.- Official websiteFrom public sourcesfrom catalog metadatamemvid.com/ ↗
- Language package registrynodejsFrom public sourcesfrom the package manifest — publication on the registry is not verified
npm install claude-brainNot verified: check that this package in the registry belongs to this project before installing.
www.npmjs.com/package/claude-brain ↗ - Build from sourceFrom public sourcesfrom catalog metadata
Build from source: no validated build recipe — follow the repository instructions.
github.com/memvid/claude-brain ↗
Compatibility
Unknown means no evidence was found — not that the product is incompatible.| Platform | Status | Architecture | Evidence | Confidence |
|---|---|---|---|---|
| Claude Code | Unknown | — | — | — |
| Claude (web & desktop) | Unknown | — | — | — |
| OpenAI Codex | Unknown | — | — | — |
| ChatGPT | Unknown | — | — | — |
| Cursor | Unknown | — | — | — |
| GitHub Copilot | Unknown | — | — | — |
| Gemini CLI | Unknown | — | — | — |
| Node.js | Compatible | — | package manifest: package.json name | 0.60 |
Releases
checked Oct 30, 2026Files in 1.0.7
This release has no attached files.
Release history
- v1.0.2Dec 18, 2025Official source ↗
Quality profile
algorithm quality-v1.0 · assessed Oct 16, 2026Score components
License
MITThis is the catalog policy status, not legal advice.
Sources
Reviews
No reviews yet.
Alternatives
README
From memvid/claude-brain · license MIT · fetched Oct 30, 2026Give Claude Code photographic memory.
https://github.com/user-attachments/assets/b57cb3db-576b-4c1f-af92-95796ba3fb5b
Install in 30 seconds · How it Works · Commands · Full Demo
The Problem
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.
The Fix
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.
Installation
# One-time setup (if you haven't used GitHub plugins before)
git config --global url."https://github.com/".insteadOf "git@github.com:"
# In Claude Code
/plugin add marketplace memvid/claude-brain
Then: /plugins → Installed → mind Enable Plugin → Restart.
Done.
How it Works
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:
- Session context, decisions, bugs, solutions
- Auto-injected at session start
- Searchable anytime
Why one file?
git commit→ version control Claude's brainscp→ transfer anywhere- Send to teammate → instant onboarding
Commands
In 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.
CLI (Optional)
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
FAQ
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.