Skip to content

Github · GitHub Repository Radar

memvid claude-brain

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.

Stars

576

Inactive

Forks

60

Watchers: 575

Repository Radar Score

34 / 100

Growth

7d
+0
30d
+0
%
0.0%

Not enough metric snapshots yet to chart growth for this repository.

Last observed: 4 days ago

Score breakdown

  • popularity 49
  • growth 0
  • activity 15
  • freshness 100
  • community 66

Need help integrating this stack?

Our team builds with modern open-source stacks. Tell us what you are shipping.

Get a quote →
Claude Brain

Give Claude Code photographic memory.


video.mp4

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 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:

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 →


FAQ

How big is the file?

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

Is it private?

100% local. Nothing leaves your machine. Ever.

How fast?

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

Reset memory?

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.

Created: Dec 18, 2025

Last push: Jan 19, 2026

Default branch: main

Latest release: v1.0.7

Languages

Share of the codebase by language, based on repository metadata from the host.

  • TypeScript 51.7%
  • JavaScript 48.3%

Repository Radar analysis

Deterministic insights derived from public metadata and our observations — not personal testing or reviews.

Why this repository is interesting

  • Listed in our discovery index with public GitHub metadata for analysis.

Who should use it

  • Developers working primarily with TypeScript
  • Teams exploring AI tooling, agents, or ML infrastructure

Potential use cases

  • Reference or evaluate TypeScript open-source approaches in this domain
  • Prototype AI/agent workflows or study reference architectures

Strengths

  • README present in our index
  • Declared license: MIT License

Limitations / considerations

  • Insights are derived from public metadata and our observations — not a substitute for code review

What to watch

  • Radar Score is modest — dig into activity and docs before committing

Source: GitHub (public metadata) + Repository Radar analysis. We do not claim ownership of third-party repositories.

Ready to ship something that compounds?

Share your roadmap. We’ll come back with scope options, timeline ranges, and who from Shriram IT Ventures should be in the room.

Popular with product teams