The Promise
What if your AI assistant actually knew you?
Not the surface-level "you mentioned you like coffee" kind of knowing. I mean really knew you:
- Every project you're working on
- Your goals for the next year
- Your writing voice and preferences
- The ideas you captured three months ago but haven't developed yet
- The patterns in how you think and work
This guide shows you how to build exactly that.
I've been running what feels like a mini AGI on my laptop for the past few months. It's not actual AGI - let's be clear - but it's the closest thing I've experienced to having an intelligent system that understands my work, my preferences, and my context.
The setup: Claude Code connected to an Obsidian vault via MCP (Model Context Protocol).
That's it. But the implications change everything about how you work with AI.
Why This Matters
The Problem Everyone Has
AI assistants are stateless. They forget everything between sessions.
You explain your project. You describe your goals. You share your preferences. Then the next day, you start over from zero.
This creates two massive problems:
1. Context loss
You spend the first 10 minutes of every session re-explaining who you are and what you're working on
2. No compounding
The AI can't build on what it learned yesterday. Can't reference decisions you made last week. Can't connect patterns across your work.
The Solution
Give AI access to a persistent knowledge base that YOU control.
Instead of hoping AI will somehow retain context, give it access to a structured system that you maintain. Your accumulated knowledge, your projects, your preferences - all in one place that AI can reference.
The key insight: AI doesn't need to "remember" if it can "look up."
What This System Does
When I open a terminal and start Claude Code, it has access to:
- My entire Second Brain - 500+ notes across projects, ideas, philosophies, daily captures
- Project files and context - What I'm building, the status of each project, my todo lists
- Brand strategy and voice guides - How I want to communicate, what I stand for
- Historical context - Past decisions, learnings, patterns I've identified
- Daily captures - Raw thoughts, ideas, observations from throughout each day
It's like having a highly competent chief of staff who has read everything you've ever written and remembers all of it perfectly.
The Architecture
My setup uses three components working together:
Component 1: Obsidian (Your Second Brain)
A folder of markdown files organized by:
| Folder | Purpose |
|---|---|
| Daily Notes | Where I dump everything throughout the day |
| Product Projects | Organized by active products and initiatives |
| Lifelong Projects | Ongoing areas (health, brand, systems, wealth) |
| Knowledge Domains | Frameworks, learnings, reference material |
The beauty of Obsidian: it's just plain markdown files in folders. No proprietary format. No lock-in. Any tool that can read files can access your knowledge.
Component 2: Claude Code
Anthropic's terminal-based Claude interface. Unlike the web chat, Claude Code can:
- • Read and write files on your computer
- • Execute terminal commands
- • Connect to external tools via MCP (Model Context Protocol)
- • Maintain context across a working session
It's Claude, but with hands. It can actually do things.
Component 3: Filesystem MCP Server
The bridge between Claude Code and your files.
MCP (Model Context Protocol) is Anthropic's standard for connecting AI to external tools and data sources. The filesystem server specifically gives Claude Code secure, scoped access to folders you specify.
You control exactly which folders Claude can see. Everything else stays private.
Step-by-Step Setup Guide
Prerequisites
Before you start, make sure you have:
- ☐Obsidian installed (or any folder of markdown files)
- ☐Node.js installed (v18 or higher recommended)
- ☐A Claude subscription (Claude Code requires API access)
- ☐Basic comfort with terminal/command line
Step 1: Install Claude Code
Open your terminal and run:
npm install -g @anthropic-ai/claude-codeVerify the installation:
claude --versionStep 2: Set Up Your Second Brain Structure
If you're starting fresh, create this basic folder structure:
Second-Brain/ ├── Daily Notes/ │ └── 2026-01-22.md ├── Projects/ │ └── My-Project/ │ ├── _PROJECT_PLAN.md │ └── _TODOS.md ├── Knowledge/ │ └── (your learnings and reference material) └── CLAUDE.md
The key file is CLAUDE.md at the root - we'll create that in Step 4.
Step 3: Configure the Filesystem MCP Server
Claude Code needs to know where your Second Brain lives. Create or edit your MCP configuration file:
Config file location:
- Mac: ~/.config/claude-code/mcp.json
- Windows: %APPDATA%\claude-code\mcp.json
- Linux: ~/.config/claude-code/mcp.json
Add this configuration (replace the path with your actual folder):
{
"mcpServers": {
"second-brain": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/path/to/your/Second-Brain"
]
}
}
}Step 4: Create Your CLAUDE.md File
This is the magic ingredient. Create a file called CLAUDE.md in the root of your Second Brain.
This file is like a system prompt that Claude reads automatically when working in your vault. It tells Claude who you are, how your system is organized, and how to help you.
# CLAUDE.md - System Instructions ## Who I Am [Your name and what you're building. 2-3 sentences.] ## How This System Is Organized ### Daily Notes - Location: `Daily Notes/YYYY-MM-DD.md` - Purpose: Raw captures, brain dumps, meeting notes ### Projects - Location: `Projects/[Project-Name]/` - Each project has: - `_PROJECT_PLAN.md` - Goals, vision, context - `_TODOS.md` - Active tasks ## How to Help Me When I ask for help with content: 1. Check my content schedule if one exists 2. Reference my voice/style guides if available 3. Pull from my idea backlog for inspiration ## My Preferences - I prefer [direct/conversational/formal] communication - Always [preference 1] - Never [anti-preference 1]
Step 5: Test the Connection
Open your terminal, navigate to your Second Brain folder, and start Claude Code:
cd /path/to/your/Second-Brain claude
Ask Claude to read your CLAUDE.md:
Read my CLAUDE.md file and tell me what you understand about my system.If Claude can read the file and describe your setup, you're connected.
Daily Workflows: How I Actually Use This
Morning: Content Creation
I tell Claude what content is due today, and we collaborate on creating it.
Let's create today's LinkedIn post. Check my content schedule and idea backlog for what's planned.Claude pulls: the content schedule, my brand voice guide, my idea backlog, and recent daily notes. I get a draft that already sounds like me.
Evening: Processing Brain Dumps
Throughout the day, I dump raw thoughts into my daily note. In the evening:
Process today's daily note. Extract tasks, route ideas, identify any insights worth developing.What used to take 20 minutes of manual sorting happens in 2.
Project Work: Context-Aware Assistance
When I switch to a specific project:
Let's work on the Blue Orchid project. What's the current status and what should I focus on?No re-explaining. It already knows.
The Results
10+ min → 30s
Context loading time
20+ min → 2 min
Daily processing time
The biggest shift is psychological. I no longer feel like I'm working with an AI. I feel like I'm working with a system that knows me.
The compounding effect is real. Every note I write makes the system smarter. Every idea I capture is available later. Nothing falls through the cracks.
What's Next
This system is the foundation for something bigger.
I'm building Chairman - an AI that acts as your Chief of Staff. It understands your goals, manages your projects, generates daily briefings, and helps you stay aligned with what matters.
Chairman takes the ideas in this blueprint and productizes them:
- • Onboarding that captures your horizons
- • Daily briefings that surface what matters today
- • Intelligent routing of tasks and ideas
- • Plan mode that helps you create and execute strategies
Your Turn
You now have everything you need to build your own mini AGI:
- Obsidian or a markdown folder - Your knowledge base
- Claude Code - The AI interface
- Filesystem MCP - The connection layer
- CLAUDE.md - Your system prompt
The goal isn't a perfect system. It's a system that grows with you.
Get More
I share technical deep-dives, AI workflows, and lessons from building in public every week.