Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

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... show more

NeilXbt

15,966 subscribers

32,130 Aufrufe • vor 3 Monaten •via X (Twitter)

Bildung Gesundheit & Wellness Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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 a vault note, and writing connections to related knowledge. The structured artifact lands in a shared Obsidian vault of plain Markdown files readable by any tool without API integration or vendor lock-in. The hard-won operational insight that leaves with the person who found it now stays in the vault permanently. Bookmark this so you do not lose it! Follow NeilXbt for more n8n and Claude builds that solve the knowledge problem.

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 a vault note, and writing connections to related knowledge. The structured artifact lands in a shared Obsidian vault of plain Markdown files readable by any tool without API integration or vendor lock-in. The hard-won operational insight that leaves with the person who found it now stays in the vault permanently. Bookmark this so you do not lose it! Follow NeilXbt for more n8n and Claude builds that solve the knowledge problem.

NeilXbt

14,798 Aufrufe • vor 2 Monaten

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.

Simplifying AI

68,025 Aufrufe • vor 23 Tagen

Obsidian + Claude Code is how Andrej Karpathy turns 15 years of notes into a brain that works while he sleeps. The method behind it costs $0 and takes 5 minutes a day and it outlived every productivity app since 2011. Every idea, link, and half-thought gets appended to the top of a single note, with no sorting, no folders, no tags. Once a week he scrolls through, and anything that still matters gets copied back to the top. Weak ideas sink. Strong ideas resurface 5, 10, 20 times and by the 20th pass your brain has already wired them into everything else you know. Repetition as a filter. That's the whole system. Now the 2026 upgrade almost nobody is running: Drop that note into an Obsidian vault and open the folder with Claude Code not the chat app, the terminal agent that reads files. 3 commands change everything: read my last 30 days of notes and find the 3 ideas I keep circling without acting on link every note mentioning this project into a CLAUDE.md of what I actually believe about it draft this week's post from the idea that resurfaced most Claude Code doesn't search your vault it walks it, follows the wikilinks, and hands you the patterns you were too close to see. Karpathy method filters the signal, Obsidian stores it, Claude Code compounds it. One is a habit, one is a folder, one is $20 a month together they're the closest thing to a second brain that thinks back. Most people collect notes for 10 years and never read them once. His notes read him.

Obsidian + Claude Code is how Andrej Karpathy turns 15 years of notes into a brain that works while he sleeps. The method behind it costs $0 and takes 5 minutes a day and it outlived every productivity app since 2011. Every idea, link, and half-thought gets appended to the top of a single note, with no sorting, no folders, no tags. Once a week he scrolls through, and anything that still matters gets copied back to the top. Weak ideas sink. Strong ideas resurface 5, 10, 20 times and by the 20th pass your brain has already wired them into everything else you know. Repetition as a filter. That's the whole system. Now the 2026 upgrade almost nobody is running: Drop that note into an Obsidian vault and open the folder with Claude Code not the chat app, the terminal agent that reads files. 3 commands change everything: read my last 30 days of notes and find the 3 ideas I keep circling without acting on link every note mentioning this project into a CLAUDE.md of what I actually believe about it draft this week's post from the idea that resurfaced most Claude Code doesn't search your vault it walks it, follows the wikilinks, and hands you the patterns you were too close to see. Karpathy method filters the signal, Obsidian stores it, Claude Code compounds it. One is a habit, one is a folder, one is $20 a month together they're the closest thing to a second brain that thinks back. Most people collect notes for 10 years and never read them once. His notes read him.

Spike 1%

12,467 Aufrufe • vor 1 Monat

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

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,186 Aufrufe • vor 2 Monaten

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.

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 Aufrufe • vor 1 Monat

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 Aufrufe • vor 2 Monaten

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

chewa.

13,367 Aufrufe • vor 1 Monat

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.

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 Aufrufe • vor 2 Monaten

THE CREATOR OF OBSIDIAN JUST SHIPPED HIS OWN CLAUDE SKILLS PACK 44,000 developers already installed it. most people building second brains with claude have no idea it exists these aren't community skills. they're written by kepano himself - the person who built obsidian. that means they respect obsidian's actual conventions: markdown, bases, JSON canvas, backlinks, plugins, all of it drop them into your claude skills folder once. next time you say "summarize my notes about karpathy" or "extract this article to my inbox," the right skill wakes up automatically. no prompt engineering. no manual context. no config i tested 10 claude + obsidian repos to write my full breakdown. this is the one with the highest trust factor - because the person shipping it is the one who defined what an obsidian vault even looks like the full ranked breakdown of all 10 is in the article i test things like this on myself and share the results. follow kai if you want to see what's next

THE CREATOR OF OBSIDIAN JUST SHIPPED HIS OWN CLAUDE SKILLS PACK 44,000 developers already installed it. most people building second brains with claude have no idea it exists these aren't community skills. they're written by kepano himself - the person who built obsidian. that means they respect obsidian's actual conventions: markdown, bases, JSON canvas, backlinks, plugins, all of it drop them into your claude skills folder once. next time you say "summarize my notes about karpathy" or "extract this article to my inbox," the right skill wakes up automatically. no prompt engineering. no manual context. no config i tested 10 claude + obsidian repos to write my full breakdown. this is the one with the highest trust factor - because the person shipping it is the one who defined what an obsidian vault even looks like the full ranked breakdown of all 10 is in the article i test things like this on myself and share the results. follow kai if you want to see what's next

kai

255,770 Aufrufe • vor 21 Tagen

PSYCHO CREATED A GOD-MODE SECOND BRAIN ON FABLE 5 THAT FILLS ITS OWN KNOWLEDGE GAPS WHILE YOU SLEEP. KARPATHY'S FILE STRUCTURE MAKES IT POSSIBLE. Everyone wires Claude into Obsidian, posts the graph, and stops. this guy added a third system and it quietly changes the whole game: The full build is in the article below: vault structure, the Claude wiring, the exact prompts, the skills. > Obsidian as the knowledge base, but any notes app works as long as Claude Code can see the files > Karpathy's LLM Wiki doc as the skeleton, so the vault is organized the way a model actually reads, not the way humans decorate folders > a self-learning skill on a weekly loop: scans the entire brain, finds the gaps, then researches YouTube and Google by itself to fill them Read the third one again, actually your notes only ever contain what you happened to write down, and the gap-finder breaks that ceiling: the brain starts knowing things you never told it. Most second brains know what you told them. a real one notices what you didn't. that's the difference between note-taking and compounding. one sits there. the other gets smarter every week whether you showed up or not. P.S. send the article straight to your Claude, tell it to interview you, and the brain starts filling itself tonight.

PSYCHO CREATED A GOD-MODE SECOND BRAIN ON FABLE 5 THAT FILLS ITS OWN KNOWLEDGE GAPS WHILE YOU SLEEP. KARPATHY'S FILE STRUCTURE MAKES IT POSSIBLE. Everyone wires Claude into Obsidian, posts the graph, and stops. this guy added a third system and it quietly changes the whole game: The full build is in the article below: vault structure, the Claude wiring, the exact prompts, the skills. > Obsidian as the knowledge base, but any notes app works as long as Claude Code can see the files > Karpathy's LLM Wiki doc as the skeleton, so the vault is organized the way a model actually reads, not the way humans decorate folders > a self-learning skill on a weekly loop: scans the entire brain, finds the gaps, then researches YouTube and Google by itself to fill them Read the third one again, actually your notes only ever contain what you happened to write down, and the gap-finder breaks that ceiling: the brain starts knowing things you never told it. Most second brains know what you told them. a real one notices what you didn't. that's the difference between note-taking and compounding. one sits there. the other gets smarter every week whether you showed up or not. P.S. send the article straight to your Claude, tell it to interview you, and the brain starts filling itself tonight.

Miraqle

41,307 Aufrufe • vor 1 Monat

THE OBSIDIAN CEO BUILT 5 CLAUDE CODE SKILLS, AND NOW A 2,400 NOTE VAULT CAN SORT ITSELF AT 7 A.M., FIX BROKEN LINKS, AND RESURFACE IDEAS FROM 2019 IN 10 SECONDS 00:06 he loads the obsidian skill inside claude code, and the graph stops being decoration. claude can read markdown, follow backlinks, edit canvas files, repair dead links, pull project context, and move through the vault like it understands the workspace instead of guessing from one prompt. most people do not have a note problem. they have an abandoned memory problem: 800 notes, 12 folders, 40 unfinished drafts, and a beautiful graph view that never actually helps. the article shows a 33 year old editor with 2,400 markdown files, 8 years of thinking, and zero useful access for a full year. that is why the ceo angle matters. this is not another random plugin. it is claude code learning obsidian’s actual language: backlinks, daily notes, canvas boards, raw captures, processed ideas, broken references, and old drafts buried so deep they might as well be gone. a real system only needs a few rules. one inbox for messy thoughts, one raw folder nobody edits, three backlinks on every new note, and a 7 a.m. run that sorts yesterday before you even open the laptop. weekly synthesis is where it gets dangerous. claude can compress 7 days of notes into one file with themes, contradictions, abandoned ideas, repeated promises, and the exact old note where the next article was hiding. bookmark this before your second brain becomes 2,400 dead files with a pretty graph.

THE OBSIDIAN CEO BUILT 5 CLAUDE CODE SKILLS, AND NOW A 2,400 NOTE VAULT CAN SORT ITSELF AT 7 A.M., FIX BROKEN LINKS, AND RESURFACE IDEAS FROM 2019 IN 10 SECONDS 00:06 he loads the obsidian skill inside claude code, and the graph stops being decoration. claude can read markdown, follow backlinks, edit canvas files, repair dead links, pull project context, and move through the vault like it understands the workspace instead of guessing from one prompt. most people do not have a note problem. they have an abandoned memory problem: 800 notes, 12 folders, 40 unfinished drafts, and a beautiful graph view that never actually helps. the article shows a 33 year old editor with 2,400 markdown files, 8 years of thinking, and zero useful access for a full year. that is why the ceo angle matters. this is not another random plugin. it is claude code learning obsidian’s actual language: backlinks, daily notes, canvas boards, raw captures, processed ideas, broken references, and old drafts buried so deep they might as well be gone. a real system only needs a few rules. one inbox for messy thoughts, one raw folder nobody edits, three backlinks on every new note, and a 7 a.m. run that sorts yesterday before you even open the laptop. weekly synthesis is where it gets dangerous. claude can compress 7 days of notes into one file with themes, contradictions, abandoned ideas, repeated promises, and the exact old note where the next article was hiding. bookmark this before your second brain becomes 2,400 dead files with a pretty graph.

Gipp 🦅

17,790 Aufrufe • vor 1 Monat

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 Aufrufe • vor 1 Monat

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.

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 Aufrufe • vor 2 Monaten

Obsidian just became the most dangerous folder on your computer, and Andrej Karpathy predicted it with 1 markdown file. His method is called append-and-review. He described it years ago and almost nobody listened: 1 single note, every thought appended to the top, reviewed on random scrolls. No tags, no folders, no Notion dashboards with 40 linked databases. The problem was always the same the note remembers, but it can't act. That changed the moment people pointed Claude Code at an Obsidian vault. Here's the setup that's quietly spreading: Part 1 — The vault becomes a database. Obsidian stores everything as plain markdown on your disk, which means Claude Code can read it like a codebase. You open a terminal inside the vault folder and your 2,000 notes turn into queryable memory. Part 2 — The CLAUDEmd file becomes the brain stem. One file at the root tells the agent who you are, what you're building, and how your notes are structured. From that point every session starts with full context instead of a blank chat window. Part 3 — Karpathy append log becomes fuel. You dump raw thoughts all day ideas, links, half-sentences. Then 1 command at night: review today's appends, extract action items, draft the 3 posts hiding in there, link them to existing notes. The messy log goes in, structured output comes out, and the vault rewrites itself while you sleep. Part 4 — Agents start living in your notes. People are running weekly reviews, content calendars, even market research as scheduled Claude Code runs over their vault. Your second brain stops being a graveyard of highlights and starts shipping. The honest math: setup takes about 90 minutes, the first week feels like overkill, and by day 30 you're sitting on a system where every note you've written in 5 years is working for you instead of rotting in a folder. Notion needed a server, a subscription and your data on someone else's machine. Obsidian needed a text file and now the text file has an employee.

Obsidian just became the most dangerous folder on your computer, and Andrej Karpathy predicted it with 1 markdown file. His method is called append-and-review. He described it years ago and almost nobody listened: 1 single note, every thought appended to the top, reviewed on random scrolls. No tags, no folders, no Notion dashboards with 40 linked databases. The problem was always the same the note remembers, but it can't act. That changed the moment people pointed Claude Code at an Obsidian vault. Here's the setup that's quietly spreading: Part 1 — The vault becomes a database. Obsidian stores everything as plain markdown on your disk, which means Claude Code can read it like a codebase. You open a terminal inside the vault folder and your 2,000 notes turn into queryable memory. Part 2 — The CLAUDEmd file becomes the brain stem. One file at the root tells the agent who you are, what you're building, and how your notes are structured. From that point every session starts with full context instead of a blank chat window. Part 3 — Karpathy append log becomes fuel. You dump raw thoughts all day ideas, links, half-sentences. Then 1 command at night: review today's appends, extract action items, draft the 3 posts hiding in there, link them to existing notes. The messy log goes in, structured output comes out, and the vault rewrites itself while you sleep. Part 4 — Agents start living in your notes. People are running weekly reviews, content calendars, even market research as scheduled Claude Code runs over their vault. Your second brain stops being a graveyard of highlights and starts shipping. The honest math: setup takes about 90 minutes, the first week feels like overkill, and by day 30 you're sitting on a system where every note you've written in 5 years is working for you instead of rotting in a folder. Notion needed a server, a subscription and your data on someone else's machine. Obsidian needed a text file and now the text file has an employee.

Spike 1%

58,428 Aufrufe • vor 1 Monat

THIS GUY BUILT A CLAUDE CODE X OBSIDIAN MAP OF HIS ENTIRE CONTENT SYSTEM This is the useful version of “AI second brain.” Not dumping more notes. Not asking Claude for a prettier folder system. Not making a canvas because it looks smart. In the video, he points Claude Code at his Obsidian setup and shows a visual map of the actual content pipeline: Analysis Ideation Prep Scripting Prep Performance The interesting part is the shape. Each stage is connected to the next one. Some boxes show sub-processes. One section shows a router detecting content type and routing a short into the next step. There are references attached to the flow. That is a real payoff: you stop treating your vault like storage and start treating it like an inspectable machine. The move is simple: 1. Put the real workflow in markdown 2. Let Claude Code inspect the vault 3. Ask it to find stages, dependencies, and missing links 4. Turn the output into an Obsidian map 5. Use the map to see what is manual, duplicated, or broken This works because Claude Code is not just summarizing a note. It can read across prompts, docs, scripts, references, and messy process files, then expose the structure you stopped seeing. That is why the demo hits. The video is not really about “better note-taking.” It is about making your private operating system visible enough to debug. Caveat: a beautiful graph does not mean you have a working system. If the notes are vague, the map will be vague. If the process is fake, Claude will draw a fake process very cleanly. If nothing feeds back into performance, the canvas is just decoration. But if the vault already contains real work, Claude Code x Obsidian becomes a powerful audit tool. Your notes stop being a pile. They become a map of what you actually do.

THIS GUY BUILT A CLAUDE CODE X OBSIDIAN MAP OF HIS ENTIRE CONTENT SYSTEM This is the useful version of “AI second brain.” Not dumping more notes. Not asking Claude for a prettier folder system. Not making a canvas because it looks smart. In the video, he points Claude Code at his Obsidian setup and shows a visual map of the actual content pipeline: Analysis Ideation Prep Scripting Prep Performance The interesting part is the shape. Each stage is connected to the next one. Some boxes show sub-processes. One section shows a router detecting content type and routing a short into the next step. There are references attached to the flow. That is a real payoff: you stop treating your vault like storage and start treating it like an inspectable machine. The move is simple: 1. Put the real workflow in markdown 2. Let Claude Code inspect the vault 3. Ask it to find stages, dependencies, and missing links 4. Turn the output into an Obsidian map 5. Use the map to see what is manual, duplicated, or broken This works because Claude Code is not just summarizing a note. It can read across prompts, docs, scripts, references, and messy process files, then expose the structure you stopped seeing. That is why the demo hits. The video is not really about “better note-taking.” It is about making your private operating system visible enough to debug. Caveat: a beautiful graph does not mean you have a working system. If the notes are vague, the map will be vague. If the process is fake, Claude will draw a fake process very cleanly. If nothing feeds back into performance, the canvas is just decoration. But if the vault already contains real work, Claude Code x Obsidian becomes a powerful audit tool. Your notes stop being a pile. They become a map of what you actually do.

kocer

15,941 Aufrufe • vor 2 Monaten

A developer pointed Claude Code at a 6,200-note Obsidian vault and let it run overnight. The vault was 4 years of markdown. Meeting notes, half-ideas, book highlights. Dead weight. He hadn't opened 90% of it since 2022. He typed one line into the terminal. "Read everything. Find what I forgot." Then he went to bed. By 7 AM, Claude Code had touched all 6,200 files. It wrote 3 new notes. The first mapped 14 ideas scattered across 3 years into one product. He'd never seen they connected. The second listed 22 promises he'd made in old meeting notes and never kept. The third was a full essay. Stitched from 40 fragments. In his own phrasing. He hadn't written a note in 8 months. The vault had been writing itself the whole time. He just couldn't read his own handwriting at scale. Now Claude Code opens the vault every morning at 6:00. It links new notes to old ones. It flags contradictions. It drafts. 2 tools. 1 folder of plain text. No app, no cloud, no subscription. He stopped taking notes to remember them. He takes them now to be read back.

A developer pointed Claude Code at a 6,200-note Obsidian vault and let it run overnight. The vault was 4 years of markdown. Meeting notes, half-ideas, book highlights. Dead weight. He hadn't opened 90% of it since 2022. He typed one line into the terminal. "Read everything. Find what I forgot." Then he went to bed. By 7 AM, Claude Code had touched all 6,200 files. It wrote 3 new notes. The first mapped 14 ideas scattered across 3 years into one product. He'd never seen they connected. The second listed 22 promises he'd made in old meeting notes and never kept. The third was a full essay. Stitched from 40 fragments. In his own phrasing. He hadn't written a note in 8 months. The vault had been writing itself the whole time. He just couldn't read his own handwriting at scale. Now Claude Code opens the vault every morning at 6:00. It links new notes to old ones. It flags contradictions. It drafts. 2 tools. 1 folder of plain text. No app, no cloud, no subscription. He stopped taking notes to remember them. He takes them now to be read back.

Spike 1%

18,613 Aufrufe • vor 1 Monat

A 26-year-old plugged Claude Code into his Obsidian vault and the vault started working night shifts. 9,412 notes. 6 years of reading, ideas, half-dead projects. Dead weight until 3 weeks ago. He pointed Claude Code at the vault folder. No plugins. No API glue. The vault is just markdown files, and Claude Code reads files. That's the whole trick everyone misses. Now every night at 2 AM a cron job wakes Claude inside the vault: reads the 40 newest notes links them to old ones he forgot existed writes a daily brief called "what your brain missed" drafts 3 content ideas from collisions between notes Morning 1 it connected a 2021 note on Roman logistics with a 2026 note on AI agent routing. That collision became a post. 214,000 views. Morning 9 it found a SaaS idea buried in a book summary from 2022. He built the landing page the same day. 61 signups before dinner. Morning 17 it flagged that 3 of his abandoned drafts were the same idea written 3 times. He merged them. Best thing he's shipped this year. Cost: $0 in new tools. Obsidian is free. The vault was already there. 6 years he treated his second brain like a warehouse. Turns out it was an employee waiting for a boss.

A 26-year-old plugged Claude Code into his Obsidian vault and the vault started working night shifts. 9,412 notes. 6 years of reading, ideas, half-dead projects. Dead weight until 3 weeks ago. He pointed Claude Code at the vault folder. No plugins. No API glue. The vault is just markdown files, and Claude Code reads files. That's the whole trick everyone misses. Now every night at 2 AM a cron job wakes Claude inside the vault: reads the 40 newest notes links them to old ones he forgot existed writes a daily brief called "what your brain missed" drafts 3 content ideas from collisions between notes Morning 1 it connected a 2021 note on Roman logistics with a 2026 note on AI agent routing. That collision became a post. 214,000 views. Morning 9 it found a SaaS idea buried in a book summary from 2022. He built the landing page the same day. 61 signups before dinner. Morning 17 it flagged that 3 of his abandoned drafts were the same idea written 3 times. He merged them. Best thing he's shipped this year. Cost: $0 in new tools. Obsidian is free. The vault was already there. 6 years he treated his second brain like a warehouse. Turns out it was an employee waiting for a boss.

Spike 1%

147,951 Aufrufe • vor 1 Monat

Obsidian + Claude = 24/7 personal operating system Greg Isenberg just showed how to bridge a local Markdown vault and Claude Code via Obsidian CLI the setup that solves the context bottleneck: > /context - loads the complete model of your projects, schedule, and interests so you never have to re-explain details > /today - compiles calendar slots, tasks, and notes from the last week into a prioritized daily plan > /challenge - scans past entries to find contradictions, testing your current beliefs against your own history > /graduate - a custom command that Claude Code wrote for itself to extract structured essays from daily logs the people who build this tonight will never work the same way again bookmark this before your next setup session 👇

Obsidian + Claude = 24/7 personal operating system Greg Isenberg just showed how to bridge a local Markdown vault and Claude Code via Obsidian CLI the setup that solves the context bottleneck: > /context - loads the complete model of your projects, schedule, and interests so you never have to re-explain details > /today - compiles calendar slots, tasks, and notes from the last week into a prioritized daily plan > /challenge - scans past entries to find contradictions, testing your current beliefs against your own history > /graduate - a custom command that Claude Code wrote for itself to extract structured essays from daily logs the people who build this tonight will never work the same way again bookmark this before your next setup session 👇

Mr. Buzzoni

51,346 Aufrufe • vor 2 Monaten

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.

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

338,737 Aufrufe • vor 2 Monaten

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

CyrilXBT

322,843 Aufrufe • vor 2 Monaten