mind

memvid

OtherClaude Codeby memvid

Summary

Claude Brain - Give Claude photographic memory in ONE portable file

Install to Claude Code

/plugin install mind@memvid

Run in Claude Code. Add the marketplace first with /plugin marketplace add memvid/claude-brain if you haven't already.

README.md

<div align="center">

<img src="logo.png" alt="Claude Brain" width="320" />

Give Claude Code photographic memory.

![GitHub stars](https://github.com/memvid/claude-brain) ![License: MIT](https://opensource.org/licenses/MIT)

<br />

https://github.com/user-attachments/assets/b57cb3db-576b-4c1f-af92-95796ba3fb5b

<br />

Install in 30 seconds · How it Works · Commands · Full Demo

</div>

<br />

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.

<br />

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.

<br />

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.

<br />

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

<br />

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.

<br />

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

Full CLI reference →

<br />

FAQ

<details> <summary><b>How big is the file?</b></summary>

Empty: ~70KB. Grows ~1KB per memory. A year of use stays under 5MB.

</details>

<details> <summary><b>Is it private?</b></summary>

100% local. Nothing leaves your machine. Ever.

</details>

<details> <summary><b>How fast?</b></summary>

Sub-millisecond. Native Rust core. Searches 10K+ memories in <1ms.

</details>

<details> <summary><b>Reset memory?</b></summary>

rm .claude/mind.mv2

</details>

<br />

---

<div align="center">

Built on memvid - the single-file memory engine

<br />

If this saved you time, star the repo

<br />

Send me your .mv2 file and I'll tell you what's wrong with your code. No context needed - I already know everything.

</div>

Related plugins

Browse all →