Mind

Mind gives Claude a mind - not just memory across sessions, but focus within them. It remembers what worked, what didn't, and what it's supposed to be building.

When you're vibe coding with Claude, it forgets everything between sessions. What you decided, what broke, what worked - gone. Even worse, in long sessions it starts suggesting the same failed fixes over and over.

Mind fixes both problems with two-layer memory:

• MEMORY.md - Long-term memory across sessions
• SESSION.md - Short-term focus within a session

Why Mind?

4 commands + 1 prompt. Clone, sync, init, connect. Done.

Fully automated. Memory just works - no commands required:

• Claude writes memories as it works
• Session gaps auto-detected (30 min)
• Learnings auto-promoted to long-term memory
• Context auto-injected into CLAUDE.md
• Reminders auto-surface when due or when keywords match

Optional tools are there when you want them, but the core memory flow runs hands-free.

Two-layer memory:

• Cross-session recall (MEMORY.md)
• Within-session focus (SESSION.md)

Zero friction. Claude writes to files, MCP reads them lazily. No database, no cloud, no sync issues.

Human-readable. Plain .md files you can open, edit, or git-track anytime.

Open source. See exactly how it works. No black box.

Ready to Give Claude a Mind?

4 commands + 1 prompt. Zero friction.

1. Install Mind

git clone https://github.com/vibeforge1111/vibeship-mind.git
cd vibeship-mind
uv sync
uv run mind init

# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

# Windows (PowerShell)
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

2. Tell Claude Code to connect

Just paste this to Claude:

Add Mind MCP server to my config

Then in any project, say: "Let's run The Mind"

{
  "mcpServers": {
    "mind": {
      "command": "uv",
      "args": ["--directory", "/path/to/vibeship-mind", "run", "mind", "mcp"]
    }
  }
}

MCP Tools (12 total)

Core:

Type routing for mind_log():

• SESSION.md: experience, blocker, assumption, rejected
• MEMORY.md: decision, learning, problem, progress
• SELF_IMPROVE.md: feedback, preference, blind_spot, skill
• Special: reinforce (boosts pattern confidence)

Reading:

Actions:

How It Works

Long-term (MEMORY.md): Permanent knowledge - decisions, learnings, problems, progress. mind_recall() loads this as context each session.

Short-term (SESSION.md): Working memory buffer:

• Experience - Raw moments, thoughts, what's happening
• Blockers - Things stopping progress
• Rejected - What didn't work and why
• Assumptions - What you're assuming true

When a new session starts (30 min gap), valuable items get promoted from SESSION.md to MEMORY.md automatically.

See docs/HOW_IT_WORKS.md for the full architecture.

Reminders

Mind supports two types of reminders:

Time-based:

• "tomorrow", "in 3 days", "next session", "2025-12-20"

Context-based:

• "when I mention auth" - triggers when relevant keywords come up
• "when we work on database" - Claude sees keywords and surfaces reminder naturally

Example: "Remind me to check the security audit when we work on auth"

Reminders are stored in .mind/REMINDERS.md and shown in mind_recall() output.

Initialize Mind in Any Project

Run this command, replacing the paths:

uv --directory /path/to/vibeship-mind run mind init /path/to/your/project

Example (Windows):

uv --directory C:\Users\YOU\vibeship-mind run mind init C:\Users\YOU\my-project

Example (Mac/Linux):

uv --directory ~/vibeship-mind run mind init ~/my-project

Using Claude Code? Just paste this:

Run uv --directory /path/to/vibeship-mind run mind init . to set up Mind in this project

(Replace /path/to/vibeship-mind with where you cloned it)

This creates .mind/MEMORY.md and .mind/SESSION.md.

Quick Commands

# Check if everything is working
uv --directory /path/to/vibeship-mind run mind doctor

# See what Mind extracted from your notes (run from project dir, or pass path)
uv --directory /path/to/vibeship-mind run mind parse /path/to/your/project

# Check project status
uv --directory /path/to/vibeship-mind run mind status /path/to/your/project

# List all registered projects
uv --directory /path/to/vibeship-mind run mind list

The Problem This Solves

Across sessions:

• "What did we decide yesterday?" → Forgotten
• "What gotchas did we hit?" → Re-discovered every time

Within sessions:

• "Didn't we already try that?" → Suggests same failed fix 3 times
• "What are we building again?" → Drifts into rabbit holes

Mind fixes both. Two layers of memory, zero friction.

File Structure

your-project/
├── .mind/
│   ├── MEMORY.md     ← Long-term memory (persists)
│   ├── SESSION.md    ← Short-term focus (cleared each session)
│   ├── REMINDERS.md  ← Time and context-based reminders
│   ├── config.json   ← Feature flags for experiments
│   └── state.json    ← Timestamps for session detection
└── CLAUDE.md         ← Mind injects context here

Troubleshooting

Documentation

• Architecture - Technical deep-dive, design principles
• How It Works - Visual diagrams explaining the system
• MCP Tools - Full tool reference with parameters

License

Apache 2.0 - See LICENSE for details.

Built by @meta_alchemist

A vibeship.co ecosystem project