Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

OBSIDIAN TURNED 4,000+ IDEAS INTO A KNOWLEDGE GRAPH THAT REBUILDS ITSELF EVERY NIGHT every lecture adds another point. every saved article adds another signal. every old note becomes part of the map again instead of sitting dead inside a folder. a $599 mac mini runs the loop 24/7, claude... extracts the useful parts, verifies the note, then links it to 2-3 related ideas inside obsidian before saving it back into the vault. after 30 days the graph starts getting dense. random notes become clusters, forgotten ideas resurface, and the whole system begins to look less like storage and more like a private memory engine. this is what a second brain looks like when it stops waiting for you to open the app.show more

Gipp 🦅

7,867 subscribers

18,560 views • 1 month ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

THIS GUY TURNED OBSIDIAN INTO A DIGITAL TWIN OF HIS OWN BRAIN, 400 PLUS NODES, 6 KNOWLEDGE CLUSTERS, 1 LOCAL VAULT, AND A MAP THAT GETS SMARTER WITH EVERY NOTE 00:05 the graph begins as one dense sphere, then individual paths light up across the screen, showing how a single note can connect to dozens of ideas instead of disappearing inside another folder. most people store information in straight lines, one file after another. his vault grows like a network, research connects to projects, projects connect to decisions, and old notes keep feeding new work months later. after 100 notes, it still feels like storage. around 300, clusters begin exposing repeated interests, unfinished threads, and topics that keep returning even after he stops thinking about them. with claude connected, the network becomes usable context. instead of pasting 20 files into one chat, an agent can follow 5 linked notes, pull original sources, compare old decisions, and write the result back into the same vault. a real second brain is not the pretty graph. it is a local system where every new thought strengthens old connections, buried ideas come back when needed, and knowledge keeps compounding without leaving your machine.

THIS GUY TURNED OBSIDIAN INTO A DIGITAL TWIN OF HIS OWN BRAIN, 400 PLUS NODES, 6 KNOWLEDGE CLUSTERS, 1 LOCAL VAULT, AND A MAP THAT GETS SMARTER WITH EVERY NOTE 00:05 the graph begins as one dense sphere, then individual paths light up across the screen, showing how a single note can connect to dozens of ideas instead of disappearing inside another folder. most people store information in straight lines, one file after another. his vault grows like a network, research connects to projects, projects connect to decisions, and old notes keep feeding new work months later. after 100 notes, it still feels like storage. around 300, clusters begin exposing repeated interests, unfinished threads, and topics that keep returning even after he stops thinking about them. with claude connected, the network becomes usable context. instead of pasting 20 files into one chat, an agent can follow 5 linked notes, pull original sources, compare old decisions, and write the result back into the same vault. a real second brain is not the pretty graph. it is a local system where every new thought strengthens old connections, buried ideas come back when needed, and knowledge keeps compounding without leaving your machine.

Gipp 🦅

20,183 views • 1 month ago

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 views • 1 month ago

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

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

Yarchi

32,476 views • 1 month ago

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

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

Yarchi

141,580 views • 1 month ago

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,346 views • 25 days ago

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 views • 26 days ago

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

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 views • 2 months ago

Andrej Karpathy keeps his entire second brain in Obsidian 1 folder of plain text files, nothing else. Here’s the exact setup, free, that turns 1 vault into a brain you can actually query. Why most “second brains” die: Notion is a database you forget to open, ChatGPT memory wipes itself after 30 messages, and both lock your notes inside their cloud. Karpathy rule is the opposite: your notes are the 1 dataset nobody else on earth has, so keep them in plain markdown, own them forever, and let the AI read them later. 3 phases. Phase 1 — Capture with 0 friction. Install Obsidian free, local, 1 hotkey to a daily note. Dump everything into it: ideas, links, quotes, 2-line thoughts, no folders, no tags, no system. Target is 5 notes a day. Phase 2 — Let the graph connect itself. Install Smart Connections and it runs embeddings on every note you’ve ever written, so 2 notes you wrote 4 months apart and never linked by hand suddenly surface as neighbors. That’s the fireworks in the 3D graph each burst is a cluster of ideas your brain forgot it owned. Phase 3 — Query your brain. Point Claude at the vault and ask: “What did I actually think about X across all my notes?” It answers from 1,200 of your own notes, not the internet your taste, your edge, your dataset. The realistic curve looks like this: Week 1 — 40 notes, graph looks empty, feels like a waste. Month 1 — 300 notes, first real cluster forms. Month 3 — 1,200 notes, and the embeddings start surfacing links you’d long forgotten. Month 6 — you stop googling your own past ideas and just ask the vault. Before — 9 tabs, 3 note apps, 0 memory. After — 1 folder, 1,200 notes, 1 brain that compounds. The gap between people who consume and people who compound isn’t talent, it’s architecture. You build your own life so choose the right path.

Andrej Karpathy keeps his entire second brain in Obsidian 1 folder of plain text files, nothing else. Here’s the exact setup, free, that turns 1 vault into a brain you can actually query. Why most “second brains” die: Notion is a database you forget to open, ChatGPT memory wipes itself after 30 messages, and both lock your notes inside their cloud. Karpathy rule is the opposite: your notes are the 1 dataset nobody else on earth has, so keep them in plain markdown, own them forever, and let the AI read them later. 3 phases. Phase 1 — Capture with 0 friction. Install Obsidian free, local, 1 hotkey to a daily note. Dump everything into it: ideas, links, quotes, 2-line thoughts, no folders, no tags, no system. Target is 5 notes a day. Phase 2 — Let the graph connect itself. Install Smart Connections and it runs embeddings on every note you’ve ever written, so 2 notes you wrote 4 months apart and never linked by hand suddenly surface as neighbors. That’s the fireworks in the 3D graph each burst is a cluster of ideas your brain forgot it owned. Phase 3 — Query your brain. Point Claude at the vault and ask: “What did I actually think about X across all my notes?” It answers from 1,200 of your own notes, not the internet your taste, your edge, your dataset. The realistic curve looks like this: Week 1 — 40 notes, graph looks empty, feels like a waste. Month 1 — 300 notes, first real cluster forms. Month 3 — 1,200 notes, and the embeddings start surfacing links you’d long forgotten. Month 6 — you stop googling your own past ideas and just ask the vault. Before — 9 tabs, 3 note apps, 0 memory. After — 1 folder, 1,200 notes, 1 brain that compounds. The gap between people who consume and people who compound isn’t talent, it’s architecture. You build your own life so choose the right path.

Spike 1%

16,390 views • 1 month ago

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

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

shmidt

57,347 views • 1 month ago

THE OBSIDIAN GRAPH IS NOT A PRETTY NOTE MAP, IT IS A SELF-MAINTAINING AI WIKI THAT CAN TURN 120 SAVED SOURCES INTO 700 LINKED PAGES WHILE YOU ONLY KEEP ADDING NEW MATERIAL 00:11 the graph opens and the trick becomes obvious: every dot is a saved idea, every cluster is a topic, and every line is context the AI no longer has to rebuild from scratch every morning most people use chatgpt like a disposable memory slot. they upload 1 pdf, ask 3 questions, close the tab, and the next day the model knows nothing unless they feed it the same context again karpathy’s LLM wiki pattern changes the game. the model reads each new source, pulls out claims, updates old pages, creates entity files, links concepts, and marks places where newer info breaks older notes with claude code and obsidian, a single clipped article can expand into 8-20 markdown files: source summary, concept pages, people, tools, comparisons, open questions, and a running index after 60 sources, this is no longer “note taking.” it becomes a private research machine that remembers your old thinking, catches repeated angles, and gives you cited answers from your own archive bookmark this before your notes turn into a graveyard again

THE OBSIDIAN GRAPH IS NOT A PRETTY NOTE MAP, IT IS A SELF-MAINTAINING AI WIKI THAT CAN TURN 120 SAVED SOURCES INTO 700 LINKED PAGES WHILE YOU ONLY KEEP ADDING NEW MATERIAL 00:11 the graph opens and the trick becomes obvious: every dot is a saved idea, every cluster is a topic, and every line is context the AI no longer has to rebuild from scratch every morning most people use chatgpt like a disposable memory slot. they upload 1 pdf, ask 3 questions, close the tab, and the next day the model knows nothing unless they feed it the same context again karpathy’s LLM wiki pattern changes the game. the model reads each new source, pulls out claims, updates old pages, creates entity files, links concepts, and marks places where newer info breaks older notes with claude code and obsidian, a single clipped article can expand into 8-20 markdown files: source summary, concept pages, people, tools, comparisons, open questions, and a running index after 60 sources, this is no longer “note taking.” it becomes a private research machine that remembers your old thinking, catches repeated angles, and gives you cited answers from your own archive bookmark this before your notes turn into a graveyard again

Gipp 🦅

41,728 views • 1 month ago

THIS GUY BUILT A GOD-MODE SECOND BRAIN IN 3 STEPS THAT GETS SMARTER EVERY SINGLE DAY AND 10X HIS RESEARCH! Everyone hoards notes they never reopen, but he turned the dead pile into a brain that actually reads itself back, in three steps: > download Obsidian, make a vault, and point Claude Code at the folder > create two folders inside, raw-sources for everything you dump in and wiki where Claude writes the organized version, then drop in Andrej Karpathy's prompt > throw in every article, book note, meeting transcript and piece of research you ever saved and forgot Then you stop searching and start asking the wiki, "what are the gaps in my knowledge", "write me a briefing on this topic", and Claude pulls from your whole vault and answers with citations. Everyone copies the folders, but the part that actually matters is what happens next, every answer gets written back into the wiki and a weekly health check hunts for contradictions and outdated info, so it is not storage you query, it is a brain that compounds every day you use it. The full step by step guide with the Karpathy prompt and the .md files is in the article below.👇 P.S. you can send this article straight to your Claude to get the full context

THIS GUY BUILT A GOD-MODE SECOND BRAIN IN 3 STEPS THAT GETS SMARTER EVERY SINGLE DAY AND 10X HIS RESEARCH! Everyone hoards notes they never reopen, but he turned the dead pile into a brain that actually reads itself back, in three steps: > download Obsidian, make a vault, and point Claude Code at the folder > create two folders inside, raw-sources for everything you dump in and wiki where Claude writes the organized version, then drop in Andrej Karpathy's prompt > throw in every article, book note, meeting transcript and piece of research you ever saved and forgot Then you stop searching and start asking the wiki, "what are the gaps in my knowledge", "write me a briefing on this topic", and Claude pulls from your whole vault and answers with citations. Everyone copies the folders, but the part that actually matters is what happens next, every answer gets written back into the wiki and a weekly health check hunts for contradictions and outdated info, so it is not storage you query, it is a brain that compounds every day you use it. The full step by step guide with the Karpathy prompt and the .md files is in the article below.👇 P.S. you can send this article straight to your Claude to get the full context

Miraqle

15,128 views • 1 month ago

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 views • 24 days ago

HE TURNED A $599 MAC MINI INTO A CLAUDE SECOND BRAIN USING OBSIDIAN, PYTHON AND A FEW ALWAYS-ON LOOPS not a fancy SaaS dashboard. not another chat tab. a tiny box on a desk that can pull lectures, transcribe audio, read articles, clean notes and write everything into a local vault while he sleeps Steve Jobs wanted the Mac mini to be the small affordable Mac anyone could put on a desk. now that same tiny Apple box can run Claude loops 24/7, process 100+ saved links, turn 2-hour lectures into structured notes, and send a morning brief for a few dollars in API calls the real trick is the loop. trigger, do, verify, retry, stop. Claude does the thinking, Obsidian stores the memory, and the Mac mini keeps running even when nobody is touching the keyboard bookmark this before you think a second brain needs another $29/month app

HE TURNED A $599 MAC MINI INTO A CLAUDE SECOND BRAIN USING OBSIDIAN, PYTHON AND A FEW ALWAYS-ON LOOPS not a fancy SaaS dashboard. not another chat tab. a tiny box on a desk that can pull lectures, transcribe audio, read articles, clean notes and write everything into a local vault while he sleeps Steve Jobs wanted the Mac mini to be the small affordable Mac anyone could put on a desk. now that same tiny Apple box can run Claude loops 24/7, process 100+ saved links, turn 2-hour lectures into structured notes, and send a morning brief for a few dollars in API calls the real trick is the loop. trigger, do, verify, retry, stop. Claude does the thinking, Obsidian stores the memory, and the Mac mini keeps running even when nobody is touching the keyboard bookmark this before you think a second brain needs another $29/month app

Ridark

65,142 views • 1 month ago

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 views • 1 month ago

AN ANTHROPIC ENGINEER LEAKED THIS OBSIDIAN CONVENTION you start with 12 notes and one convention. 6 months later you have 2379 and every one is linked to every one it belongs next to. you never touched the graph. claude did the convention is a domain prefix at the top of every markdown file. six characters. claude reads it, knows where the note belongs, and connects it to the older ones without you ever asking you drop in a new pdf at midnight. claude reads it, writes 8 linked notes, contradicts your old note from march, dates both versions, and pins the one you actually need on top by morning your vault stops being a folder. it becomes a night sky article in the first reply i test things like this on myself and share the results. follow kai if you want to see what's next

AN ANTHROPIC ENGINEER LEAKED THIS OBSIDIAN CONVENTION you start with 12 notes and one convention. 6 months later you have 2379 and every one is linked to every one it belongs next to. you never touched the graph. claude did the convention is a domain prefix at the top of every markdown file. six characters. claude reads it, knows where the note belongs, and connects it to the older ones without you ever asking you drop in a new pdf at midnight. claude reads it, writes 8 linked notes, contradicts your old note from march, dates both versions, and pins the one you actually need on top by morning your vault stops being a folder. it becomes a night sky article in the first reply i test things like this on myself and share the results. follow kai if you want to see what's next

kai

11,994 views • 8 days ago

THIS IS WHAT 3 YEARS OF OBSIDIAN NOTES SHOULD LOOK LIKE BY NOW what you see here is thousands of connections forming a structure that didn’t exist before this is exactly what karpathy built with the llm wiki pattern, every source rewires the whole thing and new structure emerges automatically instead of you manually linking notes for years knowledge that connects itself looks nothing like a productivity system bookmark this and send it to whoever still thinks obsidian is just for taking notes

THIS IS WHAT 3 YEARS OF OBSIDIAN NOTES SHOULD LOOK LIKE BY NOW what you see here is thousands of connections forming a structure that didn’t exist before this is exactly what karpathy built with the llm wiki pattern, every source rewires the whole thing and new structure emerges automatically instead of you manually linking notes for years knowledge that connects itself looks nothing like a productivity system bookmark this and send it to whoever still thinks obsidian is just for taking notes

leopardracer

25,325 views • 1 month ago

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 views • 1 month ago

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 views • 23 days ago

KARPATHY JUST MADE EVERY SECOND BRAIN GURU LOOK STUPID an artist with zero tech background took her obsidian vault, plugged it into blender and claude and turned her notes into a 3d map of her entire city no zettelkasten course, no notion templates, no productivity system just obsidian graphs that became something you can actually see and navigate this is what happens when your second brain stops being a folder and starts being a living structure save this for when someone tells you obsidian is just for nerds ↓

KARPATHY JUST MADE EVERY SECOND BRAIN GURU LOOK STUPID an artist with zero tech background took her obsidian vault, plugged it into blender and claude and turned her notes into a 3d map of her entire city no zettelkasten course, no notion templates, no productivity system just obsidian graphs that became something you can actually see and navigate this is what happens when your second brain stops being a folder and starts being a living structure save this for when someone tells you obsidian is just for nerds ↓

leopardracer

81,692 views • 1 month ago

$THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this$

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

55,345 views • 2 months ago