Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Andrej Karpathy, OpenAI Co-founder, introduced the "LLM Wiki" - a knowledge graph inside Obsidian i built my own version for GTM and here's exactly how you can do the same: - one vault, one folder per thing your business knows: offer, buyers, voice, market map, rooms, workflows, rulings, prospects,...

EXM7777's profile picture

Machina

132,035 subscribers

29,216 Aufrufe • vor 7 Tagen •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

i simply can't comprehend why everyone isn't building this yet... Andrej Karpathy, co-founder of OpenAI, pretty much invented the modern concept of "knowledge base" let me explain to you what it means... your offers, your ad angles, your content pipeline, the way you write, every decision you already made... all of it in one place any model can skim in seconds > build the vault in Obsidian, five notes deep: the offer, the client, the voice, the playbooks, the rulings > hand each worker only its slice, the writer gets the voice note, the outreach worker gets the client note, nobody loads the whole thing > every correction you make becomes one line in the rulings note, and every worker reads it before starting, so you fix a thing once instead of forever the workers are interchangeable... the vault is the business the full system is in the article below:
0:27

i simply can't comprehend why everyone isn't building this yet... Andrej Karpathy, co-founder of OpenAI, pretty much invented the modern concept of "knowledge base" let me explain to you what it means... your offers, your ad angles, your content pipeline, the way you write, every decision you already made... all of it in one place any model can skim in seconds > build the vault in Obsidian, five notes deep: the offer, the client, the voice, the playbooks, the rulings > hand each worker only its slice, the writer gets the voice note, the outreach worker gets the client note, nobody loads the whole thing > every correction you make becomes one line in the rulings note, and every worker reads it before starting, so you fix a thing once instead of forever the workers are interchangeable... the vault is the business the full system is in the article below:

Machina

292,234 Aufrufe • vor 1 Monat

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

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

Yarchi

141,580 Aufrufe • vor 2 Monaten

i simply don't understand why nobody is building this... Andrej Karpathy, OpenAI Co-founder, introduced the "LLM Wiki" - a knowledge graph inside Obsidian i built my own version for AI UGC and here's exactly how you can do the same: - start by scraping hundreds of ads to extract hooks, scripts, voiceovers and CTAs - prompt Claude Code to turn this into an Obsidian Vault - write scripts using Fable 5 and send these to Higgsfield Supercomputer - generate avatars using Nano Banana Pro and clips with Seedance the article below teaches you how to build the full workflow step-by-step:
0:26

i simply don't understand why nobody is building this... Andrej Karpathy, OpenAI Co-founder, introduced the "LLM Wiki" - a knowledge graph inside Obsidian i built my own version for AI UGC and here's exactly how you can do the same: - start by scraping hundreds of ads to extract hooks, scripts, voiceovers and CTAs - prompt Claude Code to turn this into an Obsidian Vault - write scripts using Fable 5 and send these to Higgsfield Supercomputer - generate avatars using Nano Banana Pro and clips with Seedance the article below teaches you how to build the full workflow step-by-step:

Machina

20,427 Aufrufe • vor 19 Tagen

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

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

Yarchi

32,594 Aufrufe • vor 2 Monaten

iit's wild that this still isn't the default way people use AI. Andrew Ng, a co-founder of Google Brain, gave a talk that crossed 2 million views: stop feeding your AI a folder of notes, build it a graph it can actually think with. his point is simple, stop making your AI read the whole vault to answer one thing. give it a graph, a router that points, an index that scores, edges that link, and it walks straight to the answer. it compounds, cheaper and faster the more you add. here's the whole thing: > point Claude at your notes and have it write a tiny router, your CLAUDE.md > build an index, one line per note, so it always knows where an answer lives > keep each note to one idea, and link the ones that depend on each other > make retrieval run as code, so it scores and opens the right files before the model thinks > tell it to prove the graph beats a flat folder on speed and cost, then keep the index fresh on every write set it up once and your AI stops guessing. it already knows your world before you type a word. full 12-step guide below. bookmark this.
0:23

iit's wild that this still isn't the default way people use AI. Andrew Ng, a co-founder of Google Brain, gave a talk that crossed 2 million views: stop feeding your AI a folder of notes, build it a graph it can actually think with. his point is simple, stop making your AI read the whole vault to answer one thing. give it a graph, a router that points, an index that scores, edges that link, and it walks straight to the answer. it compounds, cheaper and faster the more you add. here's the whole thing: > point Claude at your notes and have it write a tiny router, your CLAUDE.md > build an index, one line per note, so it always knows where an answer lives > keep each note to one idea, and link the ones that depend on each other > make retrieval run as code, so it scores and opens the right files before the model thinks > tell it to prove the graph beats a flat folder on speed and cost, then keep the index fresh on every write set it up once and your AI stops guessing. it already knows your world before you type a word. full 12-step guide below. bookmark this.

KingWilliam

15,099 Aufrufe • vor 1 Monat

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

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

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.

Gipp 🦅

18,560 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.
0:22

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

Spike 1%

58,428 Aufrufe • vor 1 Monat

Most people use Claude Code like a chatbot, then wonder why it forgets everything by Tuesday. The ones quietly building $10K AI workflows give it a second brain instead, and it’s free. It’s called Obsidian. You download it, point it at one folder on your computer, and that folder becomes a vault. Every note inside it is now something Claude Code can read end to end. Open Claude in that folder and it’s connected, that simple. The trick isn’t the tool, it’s the map. 3 folders, that’s the whole system. Raw, you dump everything here. Notes, transcripts, screenshots, half thoughts, zero structure. Wiki, Claude reads the raw pile and writes clean Wikipedia style articles about it, structured, searchable, permanent. Output, when you want a deliverable, a PDF, a slide deck, a script, it pulls from the wiki and ships it. Most people skip the wiki layer and feed Claude a junk drawer of 400 files, then blame the model when the answers are garbage. The model isn’t the problem, your folder is. Give it a path it can follow and it finds anything in 1 second, give it chaos and it guesses. You don’t even have to design the structure yourself. Open the vault, tell Claude to build a file system that fits your work, and watch it organize your entire brain in one prompt. Free tool, 3 folders, a second brain that compounds while you sleep. The people falling behind are still copy pasting into a chat window.
1:57

Most people use Claude Code like a chatbot, then wonder why it forgets everything by Tuesday. The ones quietly building $10K AI workflows give it a second brain instead, and it’s free. It’s called Obsidian. You download it, point it at one folder on your computer, and that folder becomes a vault. Every note inside it is now something Claude Code can read end to end. Open Claude in that folder and it’s connected, that simple. The trick isn’t the tool, it’s the map. 3 folders, that’s the whole system. Raw, you dump everything here. Notes, transcripts, screenshots, half thoughts, zero structure. Wiki, Claude reads the raw pile and writes clean Wikipedia style articles about it, structured, searchable, permanent. Output, when you want a deliverable, a PDF, a slide deck, a script, it pulls from the wiki and ships it. Most people skip the wiki layer and feed Claude a junk drawer of 400 files, then blame the model when the answers are garbage. The model isn’t the problem, your folder is. Give it a path it can follow and it finds anything in 1 second, give it chaos and it guesses. You don’t even have to design the structure yourself. Open the vault, tell Claude to build a file system that fits your work, and watch it organize your entire brain in one prompt. Free tool, 3 folders, a second brain that compounds while you sleep. The people falling behind are still copy pasting into a chat window.

West Lord

32,845 Aufrufe • vor 2 Monaten

48 HOURS AFTER KARPATHY POSTED HIS LLM WIKI IDEA, A 26-YEAR-OLD BIRMINGHAM GRAD SHIPPED THE ONE COMMAND THAT MAKES IT WORK. IT NOW HAS 76,000 GITHUB STARS 1 command. 71.5x fewer tokens per query. 0 vector databases points graphify at any folder - codebase, docs, PDFs, screenshots, video. Tree-sitter parses the code, Claude reads the prose, the whole thing lands as a knowledge graph in graphify-out/ one flag - --obsidian - writes the entire graph as a fully-linked Obsidian vault: one markdown note per concept, every relationship a wikilink, every node linked back to its source. Drop the vault into Claude Code as a skill. Claude queries the graph instead of grepping through raw files, forever Safi Shamsi finished his MSc at Birmingham with Distinction in 2025. His thesis was a knowledge-graph RAG system for academic search. He shipped Graphify 48 hours after Karpathy's post, iterates every week, and has already been forked by Rootly AI Labs for incident data. Hacker News, Analytics Vidhya, Towards AI - all organic.76,000 stars. Three months old no neo4j server. no vector db. no embedding pipeline. no cloud. no monthly fee you're reading this on a device that could clone the repo, run one command, and have a Claude-native knowledge graph of your entire codebase in Obsidian before your next standup
16:36

48 HOURS AFTER KARPATHY POSTED HIS LLM WIKI IDEA, A 26-YEAR-OLD BIRMINGHAM GRAD SHIPPED THE ONE COMMAND THAT MAKES IT WORK. IT NOW HAS 76,000 GITHUB STARS 1 command. 71.5x fewer tokens per query. 0 vector databases points graphify at any folder - codebase, docs, PDFs, screenshots, video. Tree-sitter parses the code, Claude reads the prose, the whole thing lands as a knowledge graph in graphify-out/ one flag - --obsidian - writes the entire graph as a fully-linked Obsidian vault: one markdown note per concept, every relationship a wikilink, every node linked back to its source. Drop the vault into Claude Code as a skill. Claude queries the graph instead of grepping through raw files, forever Safi Shamsi finished his MSc at Birmingham with Distinction in 2025. His thesis was a knowledge-graph RAG system for academic search. He shipped Graphify 48 hours after Karpathy's post, iterates every week, and has already been forked by Rootly AI Labs for incident data. Hacker News, Analytics Vidhya, Towards AI - all organic.76,000 stars. Three months old no neo4j server. no vector db. no embedding pipeline. no cloud. no monthly fee you're reading this on a device that could clone the repo, run one command, and have a Claude-native knowledge graph of your entire codebase in Obsidian before your next standup

chewa.

299,992 Aufrufe • vor 1 Monat

Andrej Karpathy: "Prompting is fading away. Delete everything else and keep the graph." in 68 minutes at Stanford he explains how to build one and why it is the layer everything ends up becoming LLMs → Prompts → Agents → Graphs everything before the graph is a step the graph is where the system stops being steps most people are still perfecting the thing that goes away first same model, same tokens, and the only thing that changes is the shape you run it in watch it today, then save the full graph engineering guide below
1:08:00

Andrej Karpathy: "Prompting is fading away. Delete everything else and keep the graph." in 68 minutes at Stanford he explains how to build one and why it is the layer everything ends up becoming LLMs → Prompts → Agents → Graphs everything before the graph is a step the graph is where the system stops being steps most people are still perfecting the thing that goes away first same model, same tokens, and the only thing that changes is the shape you run it in watch it today, then save the full graph engineering guide below

Hanako

124,372 Aufrufe • vor 2 Tagen

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.
2:02

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

Gipp 🦅

17,790 Aufrufe • vor 1 Monat

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

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

Kanika

38,795 Aufrufe • vor 21 Tagen

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

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

Anthropic engineer just built a second brain that reads 3 files instead of 5,000, and cut the token bill 40% no orchestrator, no plugin, just a router file, an index, and code that scores before the model ever opens anything point claude at a flat folder of notes and every question reads all of them, that’s the default and it’s expensive this breakdown turns that exact pattern into a system anyone can run CLAUDE.md → index.md → nodes → edges → retrieval as code → memory → ship it twelve steps, one shared rule, evidence lives in the index, the model reads three files while the notes folder still holds thousands the stale index test, one line drifts and the whole graph quietly turns back into the pile it was built to escape, no exceptions save it and watch, then read the article below
0:25

Anthropic engineer just built a second brain that reads 3 files instead of 5,000, and cut the token bill 40% no orchestrator, no plugin, just a router file, an index, and code that scores before the model ever opens anything point claude at a flat folder of notes and every question reads all of them, that’s the default and it’s expensive this breakdown turns that exact pattern into a system anyone can run CLAUDE.md → index.md → nodes → edges → retrieval as code → memory → ship it twelve steps, one shared rule, evidence lives in the index, the model reads three files while the notes folder still holds thousands the stale index test, one line drifts and the whole graph quietly turns back into the pile it was built to escape, no exceptions save it and watch, then read the article below

leopardracer

37,304 Aufrufe • vor 28 Tagen

Andrew Ng built agentic knowledge graph that runs agents loops from scratch: his agents searched thousands of tools through the graph, found the "right" one by meaning, and called it agent efficiency increased by 90% here's how: step 1 → embed every tool, search by meaning - not just keywords step 2 → but "similar" ≠ "correct" - it grabs the wrong one, skips the step before it step 3 → map tools as a graph - nodes are tools, edges are what runs before what step 4 → retrieve the path, not one tool - every tool the task needs, in order step 5 → bake the process into the graph - the sequence becomes data, not a guess most agents fail here and no one knows why - 1-hour brilliant course about it watch & bookmark - then read full course about graph engineering ↓
1:04:49

Andrew Ng built agentic knowledge graph that runs agents loops from scratch: his agents searched thousands of tools through the graph, found the "right" one by meaning, and called it agent efficiency increased by 90% here's how: step 1 → embed every tool, search by meaning - not just keywords step 2 → but "similar" ≠ "correct" - it grabs the wrong one, skips the step before it step 3 → map tools as a graph - nodes are tools, edges are what runs before what step 4 → retrieve the path, not one tool - every tool the task needs, in order step 5 → bake the process into the graph - the sequence becomes data, not a guess most agents fail here and no one knows why - 1-hour brilliant course about it watch & bookmark - then read full course about graph engineering ↓

codila

16,276 Aufrufe • vor 1 Monat

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓
0:41

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

72,028 Aufrufe • vor 5 Tagen

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

322,843 Aufrufe • vor 2 Monaten

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

338,737 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,346 Aufrufe • vor 1 Monat