How This Obsidian Vault Template Gives Claude Code a Long-Term Memory

The Problem: Claude Code Forgets Everything

Claude Code is powerful, but it suffers from session amnesia. Every conversation starts from zero — no context about your goals, team, patterns, or previous decisions. You re-explain the same architecture, lose decisions made three conversations ago, and your knowledge never compounds. This GitHub template solves that by giving Claude Code a persistent brain.

The Solution: A Structured Obsidian Vault

The obsidian-mind template creates a complete knowledge management system that Claude Code can read and write to. It's not just note-taking — it's a structured graph where:

• Folders group by purpose (work, org, decisions, perf)
• Links group by meaning (work notes link to people, decisions, competencies)
• Claude maintains the graph automatically during conversations

When you start a session, Claude doesn't see a blank slate. It sees your North Star goals, active projects, recent git changes, open tasks, and the entire vault structure.

How It Works: Memory Systems and Hooks

Two memory systems work together:

1. Claude Code's built-in memory (~/.claude/) handles session preferences and quick recall
2. The vault's memory system (brain/Memories.md + topic notes) stores linked knowledge that benefits from Obsidian's graph features

Short-term context goes to Claude Code. Long-term knowledge goes to the vault.

Custom hooks create a session lifecycle:

# Example CLAUDE.md configuration for the vault
SessionStart:
  - Load North Star goals from vault/goals/North Star.md
  - Check active projects from work/active/*.md
  - Scan recent memories from brain/Memories.md
  - Review open tasks from work/tasks/*.md
  - Get full vault file listing for context

Try It Now: Commands That Change Your Workflow

Install the template and add these commands to your workflow:

# Clone the template
cd ~/Documents/Obsidian
gh repo clone breferrari/obsidian-mind engineering-brain

# Configure Claude Code to use it
# Add to your CLAUDE.md:
VAULT_PATH: "~/Documents/Obsidian/engineering-brain"
SESSION_CONTEXT_INCLUDE: ["${VAULT_PATH}/brain/Memories.md", "${VAULT_PATH}/goals/North Star.md"]

# Start a session with full context
claude code --context-file "${VAULT_PATH}/brain/SessionStart.md"

Daily commands become powerful:

• /standup → Loads North Star, active projects, open tasks, recent git changes
• /dump "Meeting notes..." → Creates linked notes for people, decisions, and brag doc entries
• /incident-capture [Slack URL] → Uses MCP servers to read threads and create full timelines
• wrap up → Verifies all notes have links, updates indexes, finds uncaptured wins

The Payoff: Compounded Knowledge

When review season arrives, the backlinks on each competency note are already your evidence trail. A note without links is treated as a bug — Claude will prompt you to connect it.

Every conversation builds on the last. You stop re-explaining. Decisions compound. Wins get tracked automatically. And Claude starts every session knowing exactly where you left off.

Integration with Existing Claude Code Features

This template works with Claude Code's existing ecosystem:

• MCP servers like slack-archaeologist can feed directly into the vault
• Git integration tracks recent changes alongside project notes
• CLAUDE.md configurations drive the session lifecycle
• Auto Mode (released in preview on 2026-03-27) can automate routine vault maintenance

Getting Started

1. Install Obsidian if you haven't already
2. Clone the template: gh repo clone breferrari/obsidian-mind
3. Configure your CLAUDE.md with the vault path and session hooks
4. Start your next Claude Code session with --context-file pointing to your vault
5. Use the built-in commands (/standup, /dump, etc.) during conversations

The template is opinionated but customizable. Change the folder structure if needed, but keep the linking philosophy: a note lives in one folder but links to many notes. Claude will maintain this graph for you.