Claude Brain

Claude Brain: From goldfish to elephant? Devs split over a one‑file “video brain”

TLDR: A new plugin gives Claude a lasting memory by saving everything to a single local file, pitching speed and privacy. Devs are split: some love the portable simplicity, while others roast a rumored QR‑in‑MP4 “video brain,” slam a risky Git setup tip, and question what “100% local” means once chats hit the cloud.

Claude Brain promises to fix the classic “goldfish with a PhD” problem by giving Claude Code a memory that lives in a single local file: .claude/mind.mv2. No cloud, no database, just one tiny “brain” you can commit to Git, scp to a teammate, and query with simple commands. Devs cheered the pitch—until the comments turned into a soap opera.

Some were intrigued, but skeptics pounced: one asked how this is different from plain old “semantic search over past chats,” while another dismissed the sales pitch as, essentially, “it’s just a file—why this format?” Then came the plot twist: a commenter claimed the “brain” is literally a video file with QR‑coded memories, with vector search jumping to the right frame. Cue memes about an AI whose brain is a YouTube of QR codes—funny, but also “why not just text?”

The biggest fire, though, was the install step: a Git config line that one commenter called “terrible advice,” warning it could break pushing to GitHub. Meanwhile, the “100% local” privacy boast got side‑eyed: critics noted that once the memory is injected into a chat, it’s going to the AI provider anyway, dubbing it Schrödinger’s privacy.

Verdict? Half the crowd loves the portable, hacker‑friendly simplicity. The other half calls it a clever gimmick with risky setup and fuzzy privacy. Either way, the goldfish vs. elephant meme has entered company Slack forever.

Key Points

  • Claude Brain is a Claude Code plugin that provides persistent, local memory stored in a single file (.claude/mind.mv2).
  • Installation is done via the Claude Code plugin marketplace (memvid/claude-brain) with an optional GitHub configuration step.
  • The system captures session context, decisions, bugs, and solutions, auto-injecting relevant memory at session start and enabling search and Q&A.
  • All data remains 100% local with no databases, cloud, or API keys; performance is sub-millisecond via a Rust core.
  • An optional memvid-cli (via npm) offers CLI access; the memory file remains small (~70KB initially, ~1KB growth per memory) and can be reset by deleting it.

Hottest takes

“Are you sure?? This sounds like terrible advice” — jstanley
“As a sales pitch this is unconvincing… Why this file format?” — skybrian
“Except for the part where it gets added to the context window and sent to anthropic’s servers?” — chmod775
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.