How to Build an AI Second Brain with Obsidian and Claude Code

Why Your Notes App Isn’t Enough Anymore

Most knowledge workers are drowning in information. You read something useful, save it somewhere, and never find it again. You meet someone important, take a note, and lose the context six months later. You journal inconsistently, in different apps, with no way to connect the dots.

The concept of a “second brain” — a personal knowledge system that captures, organizes, and surfaces information when you need it — has been around for years. But AI changes what’s actually possible. Building an AI second brain with Obsidian and Claude Code means your notes don’t just sit there. They think back at you.

This guide walks through exactly how to build that system: a connected wiki, a personal CRM, and an AI-powered journal, all living in plain markdown files and enhanced by Claude Code’s ability to read, reason, and write across your entire vault.

---

What You’re Actually Building

Before touching any tools, it helps to be clear about the three components:

• Wiki — A networked knowledge base where you store evergreen information: concepts, projects, reference material, ideas. Think of it as your external long-term memory.
• Personal CRM — A contact and relationship management layer inside Obsidian. Not a sales tool — a human tool. Notes on people you know, conversations you’ve had, follow-up items, and context that’s easy to lose.
• AI Journal — A daily notes system that Claude Code can read, synthesize, and interrogate. Ask it questions like “What’s been stressing me out this month?” or “What themes keep showing up in my work notes?”

Together, these three systems let you capture information in one place and actually use it.

---

Setting Up Obsidian as Your Foundation

Obsidian is a local-first markdown editor. Your notes are plain .md files stored on your computer — no proprietary format, no lock-in. That matters here because Claude Code can read your entire file system directly.

Install Obsidian and Configure Your Vault

Download Obsidian and create a new vault. The vault is just a folder — pick a location you can remember.

Set up this folder structure to start:

/vault
  /wiki
  /crm
  /journal
  /templates
  /inbox

The inbox folder is critical. Everything gets captured here first. You process it later. This keeps your capture flow frictionless.

Enable Core Plugins

In Settings > Core plugins, turn on:

• Templates — for consistent note structures
• Daily notes — for your journal system
• Backlinks — to see what links to each note
• Graph view — helpful for spotting patterns over time

Install Key Community Plugins

Go to Settings > Community plugins and enable these:

• Templater — More powerful than the core Templates plugin. Lets you run JavaScript inside templates.
• Dataview — Turns your vault into a queryable database using inline metadata.
• Obsidian Git — Automatic version control and backup via GitHub.

---

Building the Wiki Component

Your wiki is for knowledge that doesn’t expire. Frameworks you use, concepts you’ve learned, project documentation, research notes. The goal is that when you need something, you can find it — and when Claude Code is working in your vault, it can find it too.

Create Note Templates

Good templates make capture fast and consistent. Create a file at /templates/wiki-note.md:

---
title: {{title}}
tags: []
created: {{date}}
type: concept
related: []
---

## Summary

## Details

## Connections

## Source

The YAML frontmatter is important. Dataview reads it, and Claude Code can too. Use the type field to distinguish between concepts, projects, people, and reference notes.

Set Up Atomic Notes

Each note should cover one idea. Don’t write long documents — write small, linked notes. A note on “Spaced Repetition” shouldn’t include your entire review of a book. It should explain the concept and link to your book notes.

This approach pays off when Claude Code analyzes your vault. Smaller, focused notes are easier to reason about than 5,000-word dump files.

Use Links Generously

In Obsidian, [[note name]] creates a link to another note. Use these whenever you reference a concept, person, or project. Over time, your graph view will show you how your ideas connect — and Claude Code can follow those connections when answering questions.

---

Building the Personal CRM

This is the most underrated part of a second brain. Most people lose relationship context over time. You forget where you met someone, what they were working on, what you promised to do.

Create a Contact Template

Create /templates/contact.md:

---
name: {{title}}
company: 
role: 
email: 
tags: [person]
first-met: 
last-contact: {{date}}
relationship: acquaintance
---

## Background

## Interactions

## Follow-ups

- [ ] 

## Notes

The relationship field can be values like acquaintance, colleague, close, mentor. This lets you query contacts by relationship type using Dataview.

Log Interactions Consistently

After every meaningful conversation, open that person’s contact note and add an entry under ## Interactions:

### 2025-01-14
Caught up at coffee. They're moving into a new role at X company. 
Mentioned they're struggling with Y. Offered to send them the article on Z.

Date it. Keep it factual. This log is what makes the CRM actually useful six months later.

Query Your CRM with Dataview

In any note, you can add a Dataview query to surface contacts you haven’t spoken with recently:

TABLE last-contact, company
FROM #person
WHERE last-contact < date(today) - dur(30 days)
SORT last-contact ASC

This gives you a live list of people you’re drifting from. No separate app needed.

---

Building the AI Journal

Daily journaling is where this system gets interesting. The journal is where you process your thoughts — and where Claude Code does its most useful work.

Configure Daily Notes

Set your daily notes template in Settings > Daily notes. Point it to a template like this:

Create /templates/daily.md:

---
date: {{date:YYYY-MM-DD}}
type: daily
mood: 
energy: 
tags: [journal]
---

## Morning

### Today's focus


### What I'm carrying forward from yesterday


## Work log


## Evening

### What happened today


### What I'm grateful for


### Open loops

The mood and energy frontmatter fields let Claude Code analyze patterns across your journal over time.

Run Claude Code Against Your Journal

This is where things get powerful. With Claude Code installed and pointed at your vault, you can ask it directly:

Read my journal entries from the last 30 days in /journal. 
What recurring themes do you notice? What am I avoiding?

Or:

Look at my /journal folder. Identify the weeks where my mood 
was lowest and cross-reference with my /wiki/projects folder. 
Are there correlations with specific projects?

Claude Code reads your markdown files, reasons across them, and writes back to your vault. It can create summary notes, update frontmatter, or generate a weekly review note automatically.

---

Connecting Everything with Claude Code

Claude Code is Anthropic’s agentic coding tool. It runs in your terminal, can read and write files, execute code, and use tools — including browsing and running shell commands. For an Obsidian vault, it’s a near-perfect fit because your entire second brain is just a folder of text files.

Set Up Claude Code

Install Claude Code via npm:

npm install -g @anthropic-ai/claude-code

Navigate to your vault directory and start a session:

cd ~/vault
claude

From here, Claude Code has full read/write access to your vault files.

Write a Weekly Review Agent

One of the highest-value automations is an automated weekly review. Tell Claude Code:

Every Sunday, read all my daily journal entries from the past week 
in /journal. Also read any notes I've added to /crm this week 
(check last-contact dates). Create a weekly review note in 
/journal/reviews/ with these sections:
- Key themes from the week
- Relationships I engaged with
- Open loops that need closing
- One thing I want to carry into next week

You can save this as a prompt and run it on a schedule using a cron job or Claude Code’s built-in task features.

Build a “What Did I Learn?” Query

Ask Claude Code to build you a synthesis note on demand:

Search my /wiki folder for all notes tagged with #learning 
created in the last 90 days. Write a synthesis note that 
connects the ideas and surfaces anything that seems contradictory 
or especially interesting. Save it to /wiki/synthesis/Q1-2025.md

This turns passive note-taking into active knowledge building.

Automate CRM Follow-Up Suggestions

Claude Code can read your CRM and suggest follow-ups:

Read all contact notes in /crm. Find anyone whose last-contact 
date is more than 45 days ago AND whose relationship field is 
"close" or "mentor". Write a note in my inbox suggesting 
specific talking points based on their background and recent 
interaction logs.

This is the kind of task that takes 20 minutes manually and 30 seconds with Claude Code.

---

Where MindStudio Fits In

Claude Code is great for hands-on, interactive sessions with your vault. But sometimes you want automation that runs without you — on a schedule, triggered by an event, or connected to tools outside your local machine.

That’s where MindStudio comes in. MindStudio is a no-code platform for building AI agents that can run workflows autonomously. You can build an agent that, say, receives an email, extracts contact information, and pushes a new note to your Obsidian vault via Git sync — no manual steps required.

For second brain builders, the most practical use case is using MindStudio’s Agent Skills Plugin to give Claude Code external capabilities it doesn’t have natively. Want your journal agent to send a weekly review to your email? Call agent.sendEmail(). Want it to pull in your calendar events when writing the weekly review? Use MindStudio’s Google Workspace integration.

MindStudio has 1,000+ pre-built integrations and 200+ AI models available, so you’re not reinventing connectors every time you want to bridge your local vault to the outside world. It’s free to start at mindstudio.ai.

If you’re building AI-powered automation workflows that involve external data sources, email, or third-party tools, MindStudio handles that layer so Claude Code can stay focused on reasoning across your notes.

---

Common Mistakes to Avoid

Building a second brain fails in predictable ways. Here’s what to watch out for.

Over-engineering the folder structure

It’s tempting to build a perfect taxonomy before you have any notes. Don’t. Start with three folders — wiki, crm, journal — and add structure only when you feel genuine friction. Premature organization kills the system before it starts.

Writing notes you never read

If you’re not building links and not querying your notes, you’re just archiving. The system only works when information flows. Use Dataview queries. Ask Claude Code questions. Make your vault answer back.

Using the journal as a to-do list

Your journal is for processing, not tasking. If it fills up with task items, you’ll stop using it. Keep tasks in a separate system (OmniFocus, Todoist, whatever) and use the journal to think about your work, not manage it.

Letting Claude Code overwrite notes without review

Claude Code is capable, but it can make mistakes — especially when merging or updating existing notes. Build a habit of reviewing what it writes before accepting changes. Use Obsidian Git to check diffs before committing.

---

Frequently Asked Questions

What is a second brain and why use AI with it?

A second brain is an external knowledge management system — a trusted place to store information, ideas, and context so your biological brain doesn’t have to hold everything at once. The concept was popularized by Tiago Forte in his book Building a Second Brain. Adding AI to the system means your stored knowledge becomes queryable and interactive, not just static. Instead of searching for notes manually, you can ask questions and get synthesized answers based on everything you’ve captured.

Is Obsidian the right tool for this, or should I use Notion or Roam?

Obsidian’s key advantage here is that it stores your data as plain markdown files on your local machine. That’s what makes Claude Code integration seamless — Claude Code can read and write files directly. Notion stores data in a proprietary database, which requires API calls to access. Roam Research uses a similar local-optional approach but has a steeper learning curve. If you care about privacy, speed, and direct AI file access, Obsidian is the strongest foundation for this kind of system.

Does Claude Code have access to the internet when working with my vault?

Claude Code has tools that can access the web, but by default it operates within your file system. You can enable web access for specific tasks. For most second brain workflows — journaling, synthesis, CRM review — you don’t need internet access. Where you do (pulling in meeting notes from Google Calendar, for instance), that’s a good candidate for a MindStudio integration layer.

How do I keep my vault backed up and synced across devices?

Obsidian Git is the simplest approach for developers — it commits changes automatically to a private GitHub repo. Obsidian Sync is the official paid service ($10/month) that handles sync without any setup. For most users building this kind of system, Obsidian Git + GitHub is free, reliable, and gives you a full version history — which is especially useful when Claude Code is making changes to your files.

How long does it take to build this system?

The initial setup — installing Obsidian, creating the folder structure, setting up templates, and getting Claude Code running — takes two to four hours. The harder part is building the habit. Expect two to three weeks before the journal feels natural and four to six weeks before the wiki starts to feel genuinely useful. The CRM pays off almost immediately — after your first use of the interaction log, you’ll wonder how you managed without it.

Can I use this system without coding knowledge?

Mostly yes. Obsidian requires no coding. Claude Code requires comfort with a terminal but no actual programming. The Dataview queries shown in this guide are simple enough to copy and adapt. The one area where technical knowledge helps is if you want to automate workflows (cron jobs, integrations with external tools). For that, a no-code tool like MindStudio removes the need to write infrastructure code entirely.

---

Key Takeaways

Here’s what to walk away with:

• Structure matters more than tools. A wiki, CRM, and journal cover the three types of knowledge you need to manage: concepts, relationships, and experience.
• Plain markdown is the right foundation. Local files give you speed, privacy, and direct AI access that proprietary apps can’t match.
• Claude Code turns passive notes into active knowledge. The shift from “searching your notes” to “asking your notes questions” changes how useful the system actually is.
• Start small. Get one component working before building the next. The journal is the easiest entry point.
• Automation compounds over time. The weekly review agent, the CRM follow-up suggester — these save small amounts of time every week but pay off enormously over months.

If you want to extend this system to run automated workflows, pull in external data, or connect your vault to tools like email, calendar, or Slack, MindStudio is worth exploring. You can build agents that complement your Claude Code setup without writing infrastructure code. Try it free and see what fits.