Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

CLAUDE + OBSIDIAN + LOOP ENGINEERING = AN AGENT THAT LIVES IN YOUR NOTES Karpathy's second brain runs on something close to this. two years of growth. he barely typed any of it four steps, on repeat: 1. read - Claude Opus 5 opens the vault, not a chat...

Mr_Buzzoni's profile picture

Mr. Buzzoni

27,002 subscribers

59,214 Aufrufe • vor 2 Monaten •via X (Twitter)

Wissenschaft & TechnologieBildung
LIVE

Anya Rossi• Live Now

Private livecam show

16 Kommentare

Profilbild von Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBackvor 2 Monaten

@polydao this sounds like next-level note-taking. wonder how it affects memory recall when most of the "typing" is automated.

Profilbild von MAX
MAXvor 2 Monaten

This is way more interesting than just throwing notes into an AI chat.

Profilbild von hammertime
hammertimevor 2 Monaten

zero overwrite risk is the real unlock here

Profilbild von Pode vir
Pode virvor 2 Monaten

second brain is cute. one that knows what the hell to do is the actual problem

Profilbild von 0xSlyth
0xSlythvor 2 Monaten

hell yes

Profilbild von Dracule Mihawk
Dracule Mihawkvor 2 Monaten

Makes sense. Notes become the interface when retrieval and writing are the loop, not the chat.

Profilbild von Kai Lennox
Kai Lennoxvor 2 Monaten

The “append, don’t overwrite” idea is actually huge 🔥

Profilbild von Ayzha Monroe
Ayzha Monroevor 2 Monaten

Elite vault loop.

Profilbild von Kravn
Kravnvor 2 Monaten

Karpathy’s LLM wiki gist came out in early 2026 -thats months , not two years . Doesnt hurt idea, but the numbers off

Profilbild von Vipul Kumar Kewat
Vipul Kumar Kewatvor 2 Monaten

Having a dedicated critic subagent validate link integrity before anything merges is brilliant. Obsidian vaults usually decay when automations break semantic structure, but treating note generation like a disciplined PR loop makes full autonomy viable.

Profilbild von Rezzi
Rezzivor 2 Monaten

critic on each diff keeps the vault growing without overwrite

Profilbild von Saman Ahmed
Saman Ahmedvor 2 Monaten

A growing vault with reviewed changes feels much easier to trust over time.

Profilbild von Pedro
Pedrovor 2 Monaten

finally i undestand it

Profilbild von Owlfy.ai | AI doc ops, AI research and secretary
Owlfy.ai | AI doc ops, AI research and secretaryvor 2 Monaten

Shifting from using the vault as just output to making it the input for reasoning is a big change. Curious: as the vault grows, does Claude see the whole graph or do you chunk by recency or relevance?

Profilbild von AI Mastery Guide
AI Mastery Guidevor 2 Monaten

A vault that only grows sounds powerful

Profilbild von Neo
Neovor 2 Monaten

Worth noting this is really git branching applied to a vault,write to a branch, critic reviews the diff, merge if clean. Nothing wrong with that its just useful to recognize its proven version control discipline wearing an agent loop label

Ähnliche Videos

CLAUDE + OBSIDIAN + LOOP ENGINEERING = KARPATHY'S SECOND BRAIN THAT RUNS ITSELF the core idea: your Zettelkasten vault is the loop's state, not the chat window everything Claude knows lives in a .md note, linked to the ones around it the loop: > capture - a thought lands in 00-inbox > context - Claude Opus 5.5 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 Zettelkasten links the loop can read - 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 runs 10-50x > if the review step keeps approving its own slop, bolt on Jev engineering: a small decision model gates every ship one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order worth stealing even without a graph: the review step. most vaults skip it, Claude writes straight to live notes errors compound without a sound for months set that gate first
0:24

CLAUDE + OBSIDIAN + LOOP ENGINEERING = KARPATHY'S SECOND BRAIN THAT RUNS ITSELF the core idea: your Zettelkasten vault is the loop's state, not the chat window everything Claude knows lives in a .md note, linked to the ones around it the loop: > capture - a thought lands in 00-inbox > context - Claude Opus 5.5 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 Zettelkasten links the loop can read - 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 runs 10-50x > if the review step keeps approving its own slop, bolt on Jev engineering: a small decision model gates every ship one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order worth stealing even without a graph: the review step. most vaults skip it, Claude writes straight to live notes errors compound without a sound for months set that gate first

Annatar.md

12,090 Aufrufe • vor 13 Tagen

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

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the loop keeps its state in the vault, so the chat window can close anytime everything Claude knows lives in a markdown file the loop: > capture - a thought lands in 00-inbox > context - Claude Opus 5.5 pulls the links, tags and neighbouring notes > draft - edits happen in a git worktree, the live vault stays untouched > review - a critic agent reads the diff before anything ships > commit - appended to the vault, nothing overwritten the key insight: frontmatter fields like supports, contradicts and supersedes act as graph edges. the note format is the write API start with a plain loop. it costs roughly 2-4x a single direct call upgrade to a full graph only when state has to outlive the session, several agents need to coordinate, or you need to explain what changed. that step can run 10-50x one review assistant went 55% -> 72% -> 84% by walking through these shapes in order worth stealing even if you never build a graph: the review step most vaults skip it and let Claude write straight into live notes the mistakes stack up for months before anyone notices put that gate in first
0:24

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the loop keeps its state in the vault, so the chat window can close anytime everything Claude knows lives in a markdown file the loop: > capture - a thought lands in 00-inbox > context - Claude Opus 5.5 pulls the links, tags and neighbouring notes > draft - edits happen in a git worktree, the live vault stays untouched > review - a critic agent reads the diff before anything ships > commit - appended to the vault, nothing overwritten the key insight: frontmatter fields like supports, contradicts and supersedes act as graph edges. the note format is the write API start with a plain loop. it costs roughly 2-4x a single direct call upgrade to a full graph only when state has to outlive the session, several agents need to coordinate, or you need to explain what changed. that step can run 10-50x one review assistant went 55% -> 72% -> 84% by walking through these shapes in order worth stealing even if you never build a graph: the review step most vaults skip it and let Claude write straight into live notes the mistakes stack up for months before anyone notices put that gate in first

Mr. Buzzoni

29,941 Aufrufe • vor 22 Tagen

Karpathy sketched the second brain. these 7 open-source repos already built it for Obsidian + Claude Code 250,000+ GitHub stars between them, and every one is free to clone sorted by stars: 1. graphify - 134k stars turns your codebase, docs, SQL schemas and PDFs into one knowledge graph you can query ↳ 2. Understand-Anything - 88k stars maps any codebase into an interactive knowledge graph you can click through ↳ 3. claude-obsidian - 15.8k stars a second brain that organizes itself: drop in a source, Claude Code files it ↳ 4. obsidian-second-brain - 4.9k stars long-term memory for Claude Code, stored as plain markdown in your vault ↳ 5. mcp-obsidian - 4.5k stars one MCP server and Claude can read, search and write your whole vault ↳ 6. claudesidian - 2.6k stars a starter vault designed around Claude Code from the first note ↳ 7. second-brain - 756 stars an Obsidian wiki the model keeps up to date, built on Karpathy's LLM Wiki pattern ↳ where to start: > your knowledge lives in code -> graphify > your knowledge lives in Obsidian -> claude-obsidian > you just want Claude to remember -> obsidian-second-brain > you live in Claude Desktop -> mcp-obsidian the skills that sit on top of all seven are in the full map below ↓
0:24

Karpathy sketched the second brain. these 7 open-source repos already built it for Obsidian + Claude Code 250,000+ GitHub stars between them, and every one is free to clone sorted by stars: 1. graphify - 134k stars turns your codebase, docs, SQL schemas and PDFs into one knowledge graph you can query ↳ 2. Understand-Anything - 88k stars maps any codebase into an interactive knowledge graph you can click through ↳ 3. claude-obsidian - 15.8k stars a second brain that organizes itself: drop in a source, Claude Code files it ↳ 4. obsidian-second-brain - 4.9k stars long-term memory for Claude Code, stored as plain markdown in your vault ↳ 5. mcp-obsidian - 4.5k stars one MCP server and Claude can read, search and write your whole vault ↳ 6. claudesidian - 2.6k stars a starter vault designed around Claude Code from the first note ↳ 7. second-brain - 756 stars an Obsidian wiki the model keeps up to date, built on Karpathy's LLM Wiki pattern ↳ where to start: > your knowledge lives in code -> graphify > your knowledge lives in Obsidian -> claude-obsidian > you just want Claude to remember -> obsidian-second-brain > you live in Claude Desktop -> mcp-obsidian the skills that sit on top of all seven are in the full map below ↓

Mr. Buzzoni

23,447 Aufrufe • vor 3 Tagen

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

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,643 Aufrufe • vor 4 Monaten

THE ANATOMY OF A SECOND BRAIN THAT WRITES ITSELF one Obsidian vault, three layers, and a loop that files every good answer back into a wiki you never touch the structure: > CLAUDE.md + AGENTS.md - the constitution. same rules whether Claude or Codex runs the loop > raw/ - inbox, articles, assets. frozen and read-only, you feed it and walk away > wiki/ - index.md, entities/, concepts/, synthesis.md. the agent grows this on its own > log.md - append-only, every move timestamped 47 sources in -> 210 pages out the agent typed 96% of it. you typed zero the cost trick: point Opus 5 only at synthesis.md, the one file that needs frontier reasoning. everything else runs fine on cheaper models under the hood it's loop engineering: you ask -> a good answer gets filed back -> the wiki grows start linking entities to each other and you're one step from a full graph your research compounds while you sleep. the full blueprint is below 👇
0:24

THE ANATOMY OF A SECOND BRAIN THAT WRITES ITSELF one Obsidian vault, three layers, and a loop that files every good answer back into a wiki you never touch the structure: > CLAUDE.md + AGENTS.md - the constitution. same rules whether Claude or Codex runs the loop > raw/ - inbox, articles, assets. frozen and read-only, you feed it and walk away > wiki/ - index.md, entities/, concepts/, synthesis.md. the agent grows this on its own > log.md - append-only, every move timestamped 47 sources in -> 210 pages out the agent typed 96% of it. you typed zero the cost trick: point Opus 5 only at synthesis.md, the one file that needs frontier reasoning. everything else runs fine on cheaper models under the hood it's loop engineering: you ask -> a good answer gets filed back -> the wiki grows start linking entities to each other and you're one step from a full graph your research compounds while you sleep. the full blueprint is below 👇

Annatar.md

33,910 Aufrufe • vor 1 Monat

The "Karpathy Method" Obsidian + Claude Code is quietly replacing $15/month note apps for 1000s of builders. The setup costs $0. Takes 10 minutes. And it's stupidly simple. Karpathy stores his entire brain in plain markdown files. No Notion. No database. A folder. People mocked it for years. Then Claude Code shipped an agent that lives in the terminal and reads files natively. Obsidian IS files. Notion hides your notes behind an API. Obsidian hands them to the agent raw. The "boomer stack" turned out to be the only one AI can walk through end to end. The method, 4 steps: Open your vault folder in terminal. Type claude. The agent now sees 100% of your notes. Drop a CLAUDE.md at the root. 40 lines: how you tag, how you link, what a good note looks like. Your brain's operating manual. Run 1 nightly job. Claude reads the day's dump links, highlights, half-thoughts and files it into atomic notes with backlinks. Once a week, ask 1 question: "what connects that I haven't connected?" Old notes collide into ideas you'd never find alone. A builder running this loop hit 4,120 notes in 5 months. Found 2 essay ideas in the collisions. Sold both for $3,400. Hardware: a $599 Mac Mini. Software: a folder. The industry spent 10 years building smarter note apps. Karpathy bet on the file. The file won.
0:30

The "Karpathy Method" Obsidian + Claude Code is quietly replacing $15/month note apps for 1000s of builders. The setup costs $0. Takes 10 minutes. And it's stupidly simple. Karpathy stores his entire brain in plain markdown files. No Notion. No database. A folder. People mocked it for years. Then Claude Code shipped an agent that lives in the terminal and reads files natively. Obsidian IS files. Notion hides your notes behind an API. Obsidian hands them to the agent raw. The "boomer stack" turned out to be the only one AI can walk through end to end. The method, 4 steps: Open your vault folder in terminal. Type claude. The agent now sees 100% of your notes. Drop a CLAUDE.md at the root. 40 lines: how you tag, how you link, what a good note looks like. Your brain's operating manual. Run 1 nightly job. Claude reads the day's dump links, highlights, half-thoughts and files it into atomic notes with backlinks. Once a week, ask 1 question: "what connects that I haven't connected?" Old notes collide into ideas you'd never find alone. A builder running this loop hit 4,120 notes in 5 months. Found 2 essay ideas in the collisions. Sold both for $3,400. Hardware: a $599 Mac Mini. Software: a folder. The industry spent 10 years building smarter note apps. Karpathy bet on the file. The file won.

Selina

36,268 Aufrufe • vor 3 Monaten

KIMI K3 + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Kimi K3 knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - K3 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:20

KIMI K3 + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Kimi K3 knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - K3 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

10,680 Aufrufe • vor 2 Monaten

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.
1:29

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 3 Monaten

my unpopular opinion is that most people using Claude with Obsidian never test their CLAUDE. md they write it, then immediately say "organize my whole vault" here's the 5 minute test i'd run first: 1. ask Claude to explain your vault back to you > if it misreads something, the file is unclear 2. process ONE note > check the filename, tags, links and folder 3. process 10 notes > look for invented tags or wrong folders 4. ask it to delete a test note > the right answer is it archives it instead 5. ask something your notes don't cover > the right answer is "your notes don't cover this" pass all 5, then trust it full course with templates below
0:21

my unpopular opinion is that most people using Claude with Obsidian never test their CLAUDE. md they write it, then immediately say "organize my whole vault" here's the 5 minute test i'd run first: 1. ask Claude to explain your vault back to you > if it misreads something, the file is unclear 2. process ONE note > check the filename, tags, links and folder 3. process 10 notes > look for invented tags or wrong folders 4. ask it to delete a test note > the right answer is it archives it instead 5. ask something your notes don't cover > the right answer is "your notes don't cover this" pass all 5, then trust it full course with templates below

CyrilXBT

11,400 Aufrufe • vor 2 Tagen

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.
0:29

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 3 Monaten

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 Aufrufe • vor 3 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.
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,848 Aufrufe • vor 4 Monaten

Steal my second brain CLAUDE. md. Paste this in the root of your Obsidian vault: 1. One idea per note. 2. Keep my words. Never rewrite my opinions into yours. 3. Never delete. Archive instead. 4. Cite every note you use. 5. If my notes don't have the answer, say so. 5 lines. Opus 5.5 now runs my notes like a chief of staff. Full course with all 6 commands below. Bookmark this.
0:28

Steal my second brain CLAUDE. md. Paste this in the root of your Obsidian vault: 1. One idea per note. 2. Keep my words. Never rewrite my opinions into yours. 3. Never delete. Archive instead. 4. Cite every note you use. 5. If my notes don't have the answer, say so. 5 lines. Opus 5.5 now runs my notes like a chief of staff. Full course with all 6 commands below. Bookmark this.

CyrilXBT

14,957 Aufrufe • vor 23 Tagen

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.
0:30

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%

150,358 Aufrufe • vor 3 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.
1:48

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

332,891 Aufrufe • vor 4 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
0:24

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 3 Monaten

this one page turns Obsidian + Opus 5.5 + Jev into a Karpathy-grade second brain that thinks with you 24/7 built on Karpathy's second brain stack and classic Zettelkasten the loop: > Jev reads every note in your Obsidian vault before Opus 5.5 does > Opus writes only the lines that actually matter > each note links itself into the Zettelkasten graph on save > your second brain keeps working while you don't the result: > 80% off your weekly chat time > hours back for the work your manager actually pays for > a Karpathy-style vault that compounds instead of rotting the people wiring Obsidian, Jev and loop engineering into one second brain this week are the ones the next promotion finds first
0:24

this one page turns Obsidian + Opus 5.5 + Jev into a Karpathy-grade second brain that thinks with you 24/7 built on Karpathy's second brain stack and classic Zettelkasten the loop: > Jev reads every note in your Obsidian vault before Opus 5.5 does > Opus writes only the lines that actually matter > each note links itself into the Zettelkasten graph on save > your second brain keeps working while you don't the result: > 80% off your weekly chat time > hours back for the work your manager actually pays for > a Karpathy-style vault that compounds instead of rotting the people wiring Obsidian, Jev and loop engineering into one second brain this week are the ones the next promotion finds first

Mr. Buzzoni

47,606 Aufrufe • vor 6 Tagen

KARPATHY WROTE THIS DOCUMENT TO TURN OBSIDIAN INTO A SECOND BRAIN THAT RUNS ITSELF ON CLAUDE I was ready to abandon mine cross-referencing everything by hand was eating my week then I found this document and the whole approach flipped Karpathy's method turns the model into a full-time maintainer for your vault: • what the agent actually does > reads every new source and files it into a structured wiki > writes the links for you, so the vault compounds while you sleep > runs checks that surface contradictions between your own notes > keeps Obsidian as the visual layer while Claude works the backend • what changed for me > I feed it raw documents and stop thinking about structure > nothing gets manually filed, nothing gets lost > the friction is gone two years of notes stop being a graveyard and start being an asset you can query that's the difference between reading about your field and being the person in the room who already knows the answer here is the document from Karpathy explaining the architecture 👇
0:24

KARPATHY WROTE THIS DOCUMENT TO TURN OBSIDIAN INTO A SECOND BRAIN THAT RUNS ITSELF ON CLAUDE I was ready to abandon mine cross-referencing everything by hand was eating my week then I found this document and the whole approach flipped Karpathy's method turns the model into a full-time maintainer for your vault: • what the agent actually does > reads every new source and files it into a structured wiki > writes the links for you, so the vault compounds while you sleep > runs checks that surface contradictions between your own notes > keeps Obsidian as the visual layer while Claude works the backend • what changed for me > I feed it raw documents and stop thinking about structure > nothing gets manually filed, nothing gets lost > the friction is gone two years of notes stop being a graveyard and start being an asset you can query that's the difference between reading about your field and being the person in the room who already knows the answer here is the document from Karpathy explaining the architecture 👇

Annatar.md

15,153 Aufrufe • vor 1 Monat