Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

CLAUDE + OBSIDIAN + LOOP ENGINEERING = AN AGENT THAT LIVES INSIDE YOUR NOTES Karpathy's second brain runs on something close to this two years of growth he typed almost none of it himself • the loop, four steps on repeat > read - Claude Opus 5 opens the...

27,174 Aufrufe • vor 2 Tagen •via X (Twitter)

17 Kommentare

Profilbild von Later
Latervor 2 Tagen

On a typical vault pass, what does that 2–4x actually land at in tokens or $ per kept edit?

Profilbild von Knowix
Knowixvor 2 Tagen

I'm definitely saving this man, but I’m kinda interested in seeing how they decide when one loop should stop and another should start, especially once the vault gets really large

Profilbild von 𝑨𝒇𝒓𝒊𝒏
𝑨𝒇𝒓𝒊𝒏vor 2 Tagen

very interesting concept using claude with obsidian for knowledge management.

Profilbild von rewind
rewindvor 2 Tagen

Saving this Obsidian loop

Profilbild von Nayan Surya
Nayan Suryavor 2 Tagen

This mirrors Luhmann's Zettelkasten, but with autonomous agents. Fascinating evolution of systems thinking.

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

@polydao that's wild! I hit this exact wall building my own thing. The note-taking process changed everything for me.

Profilbild von Gregor
Gregorvor 2 Tagen

when the loop writes back to the vault, what stops old notes from slowly drifting out of sync with what claude would output today? two years feels like a long time for that to compound

Profilbild von Morgan
Morganvor 2 Tagen

how do you review the branch, diff in git or inside obsidian?

Profilbild von Aureum
Aureumvor 2 Tagen

Such a detailed yet concise guide my friend, you made my day.

Profilbild von SummerLabs
SummerLabsvor 2 Tagen

Is this a second brain or a tomb of unearned insights? When the agent does the synthesis, we often trade cognitive clarity for the mere illusion of progress.

Profilbild von ZeroMark
ZeroMarkvor 1 Tag

The interesting failure mode shows up around year three. A vault that big stops fitting in context, so the read becomes a retrieval step, and whatever ranks your notes becomes the actual second brain. Curious: plain search over the vault, embeddings, or the agent walking links?

Profilbild von Blake Murphy
Blake Murphyvor 2 Tagen

Append only is the right call, and the drift question is the one that decides whether it holds. A critic reading the diff catches contradictions at write time, not the note that was true in March and quietly stopped being true in August. Reading the vault back on a schedule, not just writing to it, is what keeps the old half honest.

Profilbild von Moysha
Moyshavor 2 Tagen

booked

Profilbild von Salise
Salisevor 2 Tagen

that four-step loop sounds super efficient. love the idea of not overwriting notes too

Profilbild von Slonski
Slonskivor 2 Tagen

critic on the diff before keep is the loop notes should grow, not get rewritten

Profilbild von catman
catmanvor 2 Tagen

The durable pattern is simple: let agents propose append-only changes, have a separate check verify the diff, and keep only measured improvements. That turns notes into a compounding system instead of a fragile prompt dump.

Profilbild von Antony Claude
Antony Claudevor 2 Tagen

this is kinda cool for personal knowledge management

Ähnliche Videos

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 2 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

Yarchi

58,591 Aufrufe • vor 3 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.

Spike 1%

12,467 Aufrufe • vor 2 Monaten

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

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