Loading video...

Video Failed to Load

Go Home

Knowledge management consultants charge thousands to build systems that fail for the same reason every time! They require someone to maintain them. This architecture requires nobody. One emoji reaction on a Slack message. n8n detecting the tag and triggering the downstream workflow. Claude extracting the insight, structuring it into...

neil_xbt's profile picture

NeilXbt

16,448 subscribers

14,798 views • 3 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

This Obsidian and Claude architecture charges nothing and removes the maintenance entirely. Obsidian stores everything as plain Markdown files. Claude Code points at the vault directory. No API integrations. No paid connectors. No configuration beyond a folder path. The gap between project management systems that get abandoned the moment life gets busy and a system that maintains itself from the notes you were already writing is not discipline or organizational skill. It is the architecture described in this article, and the afternoon it takes to build five markdown components that never need a status update meeting again.
0:27

This Obsidian and Claude architecture charges nothing and removes the maintenance entirely. Obsidian stores everything as plain Markdown files. Claude Code points at the vault directory. No API integrations. No paid connectors. No configuration beyond a folder path. The gap between project management systems that get abandoned the moment life gets busy and a system that maintains itself from the notes you were already writing is not discipline or organizational skill. It is the architecture described in this article, and the afternoon it takes to build five markdown components that never need a status update meeting again.

NeilXbt

32,130 views • 4 months ago

Most Obsidian daily note setups get abandoned by Week 3! Not because the person is undisciplined. Because the system cost more attention than it returned. This build flips the ratio. Claude generates the morning brief from your vault before you open the note. The One Thing section forces a single prioritization decision rather than a list. Captures require zero structure or filing. End of day takes five minutes. A CLAUDE.md that contains the honest version of how you actually work and what derails you. The architecture that produces better days is built around who you actually are. This is the setup right here, bookmark it now! Follow NeilXbt for more Obsidian and Claude builds that solve the week three abandonment problem every other system ignores.
0:37

Most Obsidian daily note setups get abandoned by Week 3! Not because the person is undisciplined. Because the system cost more attention than it returned. This build flips the ratio. Claude generates the morning brief from your vault before you open the note. The One Thing section forces a single prioritization decision rather than a list. Captures require zero structure or filing. End of day takes five minutes. A CLAUDE.md that contains the honest version of how you actually work and what derails you. The architecture that produces better days is built around who you actually are. This is the setup right here, bookmark it now! Follow NeilXbt for more Obsidian and Claude builds that solve the week three abandonment problem every other system ignores.

NeilXbt

29,601 views • 3 months ago

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this
0:24

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,591 views • 3 months ago

Obsidian plus Hermes Agent equals a system that thinks, remembers, and runs your life. Works while you sleep. Vault holds the knowledge. Hermes reads it. Claude reasons across it. Outputs land back in the vault as new notes. Every morning brief grounded in your actual projects. Every inbox processed automatically. Every week synthesized without effort. The personal operating system that compounds forever. Read this and Bookmark it now.
0:43

Obsidian plus Hermes Agent equals a system that thinks, remembers, and runs your life. Works while you sleep. Vault holds the knowledge. Hermes reads it. Claude reasons across it. Outputs land back in the vault as new notes. Every morning brief grounded in your actual projects. Every inbox processed automatically. Every week synthesized without effort. The personal operating system that compounds forever. Read this and Bookmark it now.

CyrilXBT

43,403 views • 3 months ago

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this
16:36

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this

Yarchi

141,580 views • 3 months ago

🚨 THIS 100% FREE GITHUB REPO JUST MADE EVERY AI NOTE-TAKING APP POINTLESS. Drop any source in article, PDF, YouTube transcript, or Journal entry. Claude reads it, links it to everything in your vault, and files it into a connected knowledge graph on your own machine. Most tools save your notes. This one connects them. Every source gets linked to everything you already know. Karpathy described the idea - 15 skills. Four vault methods. Works with Claude Code, Codex, and Gemini. Most people have years of knowledge buried in folders they open twice a year. This turns all of it into a second brain that works while you sleep. MY ARTICLE COVERS THE EXACT METHOD I BUILT TO DO THE SAME THING. Guide below!
0:23

🚨 THIS 100% FREE GITHUB REPO JUST MADE EVERY AI NOTE-TAKING APP POINTLESS. Drop any source in article, PDF, YouTube transcript, or Journal entry. Claude reads it, links it to everything in your vault, and files it into a connected knowledge graph on your own machine. Most tools save your notes. This one connects them. Every source gets linked to everything you already know. Karpathy described the idea - 15 skills. Four vault methods. Works with Claude Code, Codex, and Gemini. Most people have years of knowledge buried in folders they open twice a year. This turns all of it into a second brain that works while you sleep. MY ARTICLE COVERS THE EXACT METHOD I BUILT TO DO THE SAME THING. Guide below!

Kanika

38,795 views • 1 month ago

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.
0:22

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

Dan McAteer

174,887 views • 3 months ago

MOST PEOPLE DOWNLOAD OBSIDIAN AND USE NOTION AGAIN BY WEEK THREE. Not because Obsidian is hard. Because nobody gave them the complete picture before they started building. This masterclass is that complete picture. Empty vault → a second brain that compounds every week. Philosophy. Architecture. Linking. Daily notes. Maps of Content. Claude integration. Automated workflows. And the daily practice that makes it actually stick. Everything in one guide. Read this and bookmark it now.
0:53

MOST PEOPLE DOWNLOAD OBSIDIAN AND USE NOTION AGAIN BY WEEK THREE. Not because Obsidian is hard. Because nobody gave them the complete picture before they started building. This masterclass is that complete picture. Empty vault → a second brain that compounds every week. Philosophy. Architecture. Linking. Daily notes. Maps of Content. Claude integration. Automated workflows. And the daily practice that makes it actually stick. Everything in one guide. Read this and bookmark it now.

CyrilXBT

31,207 views • 3 months ago

5,000 notes in Obsidian and none of them producing anything Most notes never get used. Not because the information was not valuable. Because every note-taking system optimises for capturing and ignores using entirely. Someone built a five-workflow Obsidian system designed from the opposite end. The contribution rate compounds from the first processed note. Here is the full build nobody is talking about. AI IS TURNING OBSIDIAN INTO A KNOWLEDGE ENGINE. Not because it captures better. Because it retrieves better. The average person has valuable insights buried in thousands of notes they never revisit. Claude changes that. It finds forgotten connections. Surfaces relevant context. Builds decision briefs. Generates writing from accumulated knowledge. The result: Less searching. More thinking. The future of note-taking isn't saving information. It's activating it.
0:53

5,000 notes in Obsidian and none of them producing anything Most notes never get used. Not because the information was not valuable. Because every note-taking system optimises for capturing and ignores using entirely. Someone built a five-workflow Obsidian system designed from the opposite end. The contribution rate compounds from the first processed note. Here is the full build nobody is talking about. AI IS TURNING OBSIDIAN INTO A KNOWLEDGE ENGINE. Not because it captures better. Because it retrieves better. The average person has valuable insights buried in thousands of notes they never revisit. Claude changes that. It finds forgotten connections. Surfaces relevant context. Builds decision briefs. Generates writing from accumulated knowledge. The result: Less searching. More thinking. The future of note-taking isn't saving information. It's activating it.

Dami-Defi

70,601 views • 4 months ago

A DOCTOR BUILT AN AI-QUERYABLE DATABASE OF EVERY DISEASE HE KNOWS IN OBSIDIAN. THE SAME STACK CAN RUN AN ENTIRE COMPANY ON ONE PERSON'S BRAIN Zoomed out, his vault looks like a constellation. Every disease linked to its symptoms, every symptom to the conditions it shows up in, every treatment to what it treats. Adding a new case is one note that wires itself into the rest. It's a personal database, and the structure has nothing to do with medicine. It's just nodes and links. Once you see that, the same setup runs anything: > a startup that needs to remember every customer, decision, and meeting; > a school whose curriculum links to every lecture and student question; > a business where SOPs, clients, and vendors all sit in one queryable graph. Drop Claude on top, and the vault stops being a map. It becomes something you can ask, in plain English, across everything you've ever written down. Full Claude + Obsidian build in the article below. Bookmark this
0:21

A DOCTOR BUILT AN AI-QUERYABLE DATABASE OF EVERY DISEASE HE KNOWS IN OBSIDIAN. THE SAME STACK CAN RUN AN ENTIRE COMPANY ON ONE PERSON'S BRAIN Zoomed out, his vault looks like a constellation. Every disease linked to its symptoms, every symptom to the conditions it shows up in, every treatment to what it treats. Adding a new case is one note that wires itself into the rest. It's a personal database, and the structure has nothing to do with medicine. It's just nodes and links. Once you see that, the same setup runs anything: > a startup that needs to remember every customer, decision, and meeting; > a school whose curriculum links to every lecture and student question; > a business where SOPs, clients, and vendors all sit in one queryable graph. Drop Claude on top, and the vault stops being a map. It becomes something you can ask, in plain English, across everything you've ever written down. Full Claude + Obsidian build in the article below. Bookmark this

Yarchi

32,594 views • 3 months ago

You don't fully understand what this integration could turn into. Five skills. Created by the CEO of Obsidian. Released publicly. Free to add. He read it and thought about who would pay him to implement it for them. Law firms. Agencies. Medical practices. All have the same problem, knowledge that lives in someone's head until that person leaves. He builds the vault. Writes the files. Connects Claude. Delivers in three days. $2,200 once. $1,500 every month after. The pitch is one sentence: your new employee will read every process, every client file, and every decision made in the last three years before their first day. 6 clients. $9,000 a month. 10 hours of work a week. Five skills from the CEO. One business on top of them.
0:24

You don't fully understand what this integration could turn into. Five skills. Created by the CEO of Obsidian. Released publicly. Free to add. He read it and thought about who would pay him to implement it for them. Law firms. Agencies. Medical practices. All have the same problem, knowledge that lives in someone's head until that person leaves. He builds the vault. Writes the files. Connects Claude. Delivers in three days. $2,200 once. $1,500 every month after. The pitch is one sentence: your new employee will read every process, every client file, and every decision made in the last three years before their first day. 6 clients. $9,000 a month. 10 hours of work a week. Five skills from the CEO. One business on top of them.

Superior

28,320 views • 2 months ago

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic
7:55

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic

Gbenga Akindolani |AI Engineer | Automation Expert

46,436 views • 3 months ago

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Claude knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - claude pulls links, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order
0:24

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Claude knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - claude pulls links, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order

Mr. Buzzoni

137,015 views • 1 month ago

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.
0:42

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Avid

339,134 views • 3 months ago

Obsidian Bases are better than Notion databases. Most people never use them because they're too technical. This Claude skill changes this: Bases automatically aggregate notes from your vault into a structured table. I have dozens of bases; the one in the video replaces the reference manager, for instance. Problem: Most struggle with setting them up. There's now a skill built by one of the Obsidian developers that runs inside Claude. The skill scans your vault and automatically generates the base. The hardest Obsidian feature to learn. Solved with one sentence.
1:53

Obsidian Bases are better than Notion databases. Most people never use them because they're too technical. This Claude skill changes this: Bases automatically aggregate notes from your vault into a structured table. I have dozens of bases; the one in the video replaces the reference manager, for instance. Problem: Most struggle with setting them up. There's now a skill built by one of the Obsidian developers that runs inside Claude. The skill scans your vault and automatically generates the base. The hardest Obsidian feature to learn. Solved with one sentence.

Ilya Shabanov

34,406 views • 5 months ago

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.
0:30

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

10,799 views • 2 months ago

CLAUDE JUST TURNED OBSIDIAN INTO A BRAIN THAT NEVER FORGETS (FOR $0) Someone connected Claude straight to their Obsidian vault. Now the AI reads and writes every note they own. Every client, every idea, every project. Instant recall. Runs on Claude + Obsidian. One evening. Zero code. The numbers are insane: - Notion AI: $10/month forever - A "second brain" course: $500 to $2,000 - An assistant to organize your notes: $3,000/month - This setup: $0 - Time to build: one evening - Skill required: copy the steps The opportunity is even wilder: People sell Notion "second brain" templates for $99 to $499. You just built something better for free, and it never forgets. One free vault can hold the entire memory of your business: clients, content, SOPs, ideas. One person + Claude + Obsidian + one evening = an infinite memory that never forgets. Save and watch the clip.
13:03

CLAUDE JUST TURNED OBSIDIAN INTO A BRAIN THAT NEVER FORGETS (FOR $0) Someone connected Claude straight to their Obsidian vault. Now the AI reads and writes every note they own. Every client, every idea, every project. Instant recall. Runs on Claude + Obsidian. One evening. Zero code. The numbers are insane: - Notion AI: $10/month forever - A "second brain" course: $500 to $2,000 - An assistant to organize your notes: $3,000/month - This setup: $0 - Time to build: one evening - Skill required: copy the steps The opportunity is even wilder: People sell Notion "second brain" templates for $99 to $499. You just built something better for free, and it never forgets. One free vault can hold the entire memory of your business: clients, content, SOPs, ideas. One person + Claude + Obsidian + one evening = an infinite memory that never forgets. Save and watch the clip.

shmidt

57,347 views • 2 months ago

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.
1:25

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.

RetroChainer

13,775 views • 1 month ago

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.
0:55

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Spike 1%

18,223 views • 2 months ago

Fable 5 and Karpathy's knowledge base trick are basically a cheat code. Someone just dropped a full walkthrough on building the most powerful second brain ever Andrej Karpathy shared a simple idea: use an LLM to build personal knowledge bases. Index your sources, let the model organize them, and use Obsidian as the front end. Someone just built the full thing with Claude Code and Fable 5, and walked through every step You drop your sources into a folder (YouTube transcripts, PDFs, articles, meeting notes) and Claude Code reads them, splits them into linked wiki pages, and builds a living second brain that connects everything. It grows on its own as you add more. Where Fable 5 pulls ahead: it found a connection buried across two sources you'd miss reading them separately. And asked to turn the messy web of links into something a beginner could understand, it produced clean, simple HTML in one shot. The same task took a full day on Opus 4.8 and came out worse. The best part: it's all just markdown files with routing. So it's not locked to Claude Code. Plug it into Codex or any agent you want. Give your AI a real knowledge base, and it stops guessing and starts knowing. Bookmark this.
14:34

Fable 5 and Karpathy's knowledge base trick are basically a cheat code. Someone just dropped a full walkthrough on building the most powerful second brain ever Andrej Karpathy shared a simple idea: use an LLM to build personal knowledge bases. Index your sources, let the model organize them, and use Obsidian as the front end. Someone just built the full thing with Claude Code and Fable 5, and walked through every step You drop your sources into a folder (YouTube transcripts, PDFs, articles, meeting notes) and Claude Code reads them, splits them into linked wiki pages, and builds a living second brain that connects everything. It grows on its own as you add more. Where Fable 5 pulls ahead: it found a connection buried across two sources you'd miss reading them separately. And asked to turn the messy web of links into something a beginner could understand, it produced clean, simple HTML in one shot. The same task took a full day on Opus 4.8 and came out worse. The best part: it's all just markdown files with routing. So it's not locked to Claude Code. Plug it into Codex or any agent you want. Give your AI a real knowledge base, and it stops guessing and starts knowing. Bookmark this.

Shadow Nick

47,058 views • 2 months ago