Give 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.
A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages.
Standalone skills for Claude Code and Codex: product discovery, architecture, implementation, technical foundations, reviews and delivery, with explicit scope and verification.
**Install in 30 seconds** · How it Works · Commands · Full Demo The Problem **200K context window. ** You're paying for a goldfish with a PhD. Installation Then: → Installed → **mind** Enable Plugin → Restart. How it Works After install, Claude's memory lives in one file: No database. **What gets captured:** Session context, decisions, bugs, solutions Auto-injected at session start Searchable anytime **Why one file? ** → version control Claude's brain → transfer anywhere Send to teammate → instant onboarding Commands **In Claude Code:** 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: Full CLI reference → FAQ How big is the file? No context needed - I already know everything.
Frequently asked questions
How many stars and forks are recorded?
memvid/claude-brain has 578 stars and 59 forks.
What is the repository rank?
memvid/claude-brain is ranked 16,680.
What language and category are recorded?
memvid/claude-brain has 578 stars, uses TypeScript and belongs to AI Engineering.
Which repository is closest in rank?
memvid/claude-brain is compared with HoangNguyen0403/agent-skills-standard, ranked 16,686 with 577 stars.
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 brain
scp → 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:
