Claude has memory. Obsidian gives it a brain.
Claude remembers fragments. A name. A preference. What you told it last week. But it has no idea what you actually worked on, what decisions you made, or what's sitting on your plate. This guide fixes that. Wire Claude to Obsidian as a second brain, capture context with OMI, organise it with the PARA structure — and every AI agent you run becomes a hundred times more powerful. Both tools are free.

"Claude has memory, but it's weak. It remembers a name, a preference, what you told it last week. But it has no idea what you actually worked on or what's sitting on your plate. This system fixes that completely."
— Julian, opening the read-alongClaude's memory is weak. That's the whole problem.
Claude's native memory holds onto fragments. Your name. A few preferences. Sometimes the last thing you said. But the moment you start a new session it has no idea what you actually worked on yesterday, what decisions you made last week, or what's currently on your plate.
So you spend the first five minutes of every conversation re-explaining yourself. Then Claude gives you generic answers because it doesn't know your specific situation. Multiply that across every agent you use — Hermes, OpenClaw, Codex, Antigravity, Free Claude Code — and you're losing an hour a day to "context re-loading."
"The model isn't the bottleneck. The context is."
This was the question Richard asked inside the AI Profit Boardroom last week. I answered him on video. This is the cleaned-up read-along of that answer.
The three-piece stack that fixes it forever
Three tools. Each one does one thing. Together they form a continuous loop where every conversation makes the system smarter.
OMI — the capture layer
The wearable + app that listens to your day, takes notes on what you said, recorded your conversations, identified tasks. Free to use as long as you skip the OMI chat (subscription). Captures the raw context.
Obsidian — the vault
The free markdown app. Stores everything as plain text files in folders on your machine. OMI exports memories into it. Claude reads from it. Other agents read from it. Your second brain lives here forever — you own it.
Claude — the reader and the organiser
The intelligence. Two roles: read the vault for full context before answering, and organise the vault into a useful structure. Both happen automatically once wired.
Combine the three and you get a second brain that captures itself, organises itself, and feeds every AI agent you run.
OMI captures. Obsidian stores. Claude reads + organises.
— this is the loopOMI — taking notes on your day automatically
OMI is the listener. Wear it, or set it on your desk. It captures every conversation, every idea, every task you mention out loud — transcribes them, structures them, surfaces tasks, links to other apps. Yesterday I gave a coaching call; OMI captured the whole thing, surfaced 14 action items, and quietly logged them.
The killer feature for this guide: OMI exports to Obsidian. Every memory it takes on you can flow straight into a markdown file in your vault. Set it up once, forget it. From that moment on, every conversation you have in real life becomes content for your AI agents to read.
- What's free: OMI itself + the export-to-Obsidian feature
- What's paid: OMI chat (subscription). You don't need it for this setup — Claude is the brain.
Obsidian — your second brain, in markdown
Obsidian is a free note-taking app. The crucial detail: notes are stored as plain markdown files in a folder on your machine. Not a proprietary database. Not a cloud silo. Just .md files you can read in any text editor for the rest of your life.
Why this matters: every AI agent in 2026 speaks markdown. Claude reads it natively. So do Codex, Hermes, Antigravity, OpenClaw, Free Claude Code, Gemini. Your vault becomes a universal memory layer that every model can use.
The interconnection happens via [[double brackets]] — you link a note to another note, and Obsidian builds a graph view that maps the relationships. It's how the second brain becomes a brain (a network) rather than a stack of files.
Claude — the reader
Two ways to wire Claude to your vault. Pick whichever fits.
- MCP Obsidian (cleanest): Install
obsidian-mcp. Claude reads + writes the vault automatically on every conversation. Permanent connection. The pattern Free Claude Code → uses too. - Open Folder (quickest): In a fresh Claude session, click "Add to context" → "Open folder" → point at your Obsidian vault folder. Claude reads it for that session. Simple, no install. Good for trying it out first.
Once wired, you can ask: "Check through my memories and surface some ideas for what I could automate based on what I do day-to-day." Claude reads the vault, finds patterns, suggests automations rooted in your actual workflow — not generic SaaS advice.
That single shift — from generic answers to answers grounded in your real context — is the 100× multiplier. Every other improvement compounds on top of it.

The full Infinite Context Engine setup
Inside the AI Profit Boardroom: the OMI + Obsidian + Claude stack with the MCP install, the PARA template, the SOP for organising the vault, the 100 prompts, and the 30-day roadmap. Plugs into the rest of Agent OS — Hermes, Codex, Antigravity, Free Claude Code — so every agent reads from the same memory.
Get Agent OS in AIPB →Claude — the organiser
This is the move most people miss. After Claude reads your vault, ask it to reorganise it. The prompt:
"Based on my Obsidian vault, can you restructure it into a useful second brain using PARA? Create maps of content so the navigation is useful, not just tidy."
Claude will restructure the whole vault. Mine went from "untitled documents and one giant memories.md file" to a clean PARA structure with daily notes, maps of content, an SOP file, and a graph view that actually links together.
PARA — the only second-brain structure you need
PARA is Tiago Forte's structure for second brains. Four buckets. That's it. Claude already knows it — you don't need to teach it the rules.
Projects
Active work with a defined outcome and deadline. "Launch AIPB Q2 webinar." Closes when done. Then moves to Archive.
Areas
Ongoing responsibilities with no end date. "Health." "Marketing operations." "Client relationships." Live here permanently.
Resources
Topics of long-term interest. Reference material. Articles to save. Books you read. Frameworks worth keeping.
Archive
Everything no longer active. Old projects, retired areas, outdated resources. Searchable, but out of the way.
Claude builds you a Home dashboard at the root, a README that explains the rules (the SOP your future agents can read), and a Maps of Content file for each section. The graph view becomes meaningful. The system becomes navigable.
The flow that compounds — both directions
The system isn't read-only. It's a two-way loop:
- Vault → Claude. Every chat starts with full context. Claude pulls relevant notes, surfaces what's on your plate, references your actual decisions.
- Claude → Vault. Every chat writes back useful insights — notes on the conversation, action items, decisions, new resources. The vault grows.
So the more you use it, the smarter it gets. Every conversation feeds the next. By month 6 your second brain has more useful context on your business than you yourself can remember.
"The more you give your AI agents, the more useful they become."
This is what I call the Infinite Context Engine. Same pattern that powers The Goldie Infinite Knowledge Engine → with NotebookLM as a content multiplier on top.
Three beliefs holding you back
The setup is free. The blockers are mental.
Still not sure a second brain pays off? Read 258 unfiltered member wins from the AI Profit Boardroom →
"I'll just use Claude's native memory. It'll get better over time."
Maybe. But it's siloed in one product. The moment you switch to Gemini or Codex or Hermes, the memory is gone. Obsidian-as-vault belongs to you, and every agent you'll ever use can read it.
"Setting up a second brain is too much work."
Setting it up takes one weekend. Maintaining it takes zero effort — OMI captures while you live, Claude organises while you sleep. The first week is the only week you "work" on it. Every week after, it works on you.
"I don't have enough notes for this to matter."
You have more than you think. Slack history, email, voice memos, journal entries, old documents, OMI captures from one week. Hand them to Claude with the PARA prompt and watch what comes out. The vault grows fast once you start.
30-day roadmap
One piece per week. Each one builds on the last.
memories.md file. Don't organise it yet. Let it accumulate.obsidian-mcp). Ask Claude to surface ideas based on what it sees. Get used to context-grounded answers.The Goldie Second Brain™ — recap
Claude alone is impressive. Claude wired to a vault that captures your life and organises itself is a different category of tool. The setup is free, the maintenance is automatic, and every agent you'll ever use will pull from the same memory.
OMI captures. Obsidian stores. Claude reads + organises. PARA gives the structure. The two-way loop makes it compound. One weekend of setup, then years of leverage.
One brain. Every agent. Forever.
Inside AIPB: the full Infinite Context Engine setup, the MCP install, the PARA template, 100 prompts I use daily, the SOP for organising the vault, and the 30-day roadmap. Plus how to wire it into Hermes, Codex, Free Claude Code, and Antigravity so every agent reads from the same brain.
Join the AI Profit Boardroom →