Video wird geladen...

Video konnte nicht geladen werden

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

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

Machina

150,788 subscribers

294,839 Aufrufe • vor 2 Monaten •via X (Twitter)

Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

33 Kommentare

Profilbild von Jai Rod

Jai Rodvor 2 Monaten

I can't stand obsidian. Instead, I built a memory system (Inkstone) that every night "dreams": turns the previous day's sessions and documents into wiki, distills the wiki concepts to fts5 database which the agent can access through MCP. I dumped 3 years of Chatgpt history to it and my agents now know everything about me and my businesses.

Profilbild von Kevin | Large Fam Dad

Kevin | Large Fam Dadvor 2 Monaten

"your" content—ha! AI searching for viral posts written by other LLMs to create more AI content. A knowledgebase of 99.9% AI generated content. This is getting ridiculous.

Profilbild von TechThought.org

TechThought.orgvor 2 Monaten

For small scale, personal.. yup👍.. for larger enterprise scale .. 1000+ docs.. you need to move to a real #graph DB.

Profilbild von FAMBROjoe

FAMBROjoevor 2 Monaten

When ambient listening and ambient vision data sources connect, you gain the capacity to recall far more than your brain can manage alone… and the power to analyze language, behavior, and thinking patterns in unprecedented ways. Such applications hold profound value for both personal and professional use.

Profilbild von Curious_pleb

Curious_plebvor 2 Monaten

@Selkis_2028 I have yet to see anyone use this for anything useful (besides just being a personal wiki of articles read).

Profilbild von Sadrum

Sadrumvor 2 Monaten

Built one of these last year. The hard part isn't the KB, it's the maintenance. Mine had 40 docs; half were stale in a month. Curation is the whole job, not the storage.

Profilbild von Hamza Khalid

Hamza Khalidvor 2 Monaten

Wow ~ that's a beautiful brain, I think nodes are arranged so properly

Profilbild von David T Kramaley

David T Kramaleyvor 2 Monaten

central hub forces single source updates, saves hours on tone fixes

Profilbild von Taïga🐍

Taïga🐍vor 2 Monaten

Кто в этом всём великолепии не теряется? Я себе поднчла аналогичную систему и она мне оказалась не нужна. Только отнамала время. Я же хотела время экономить.

Profilbild von Kevin Jimoh

Kevin Jimohvor 2 Monaten

When bro doesn’t know about RAG

Profilbild von NadIs

NadIsvor 2 Monaten

ngl this sounds like a lot of work to set up a knowledge base

Profilbild von Laurent Courtines

Laurent Courtinesvor 2 Monaten

Im using @PawelHuryn product manager second brain on my project What's interesting is how the "put it in the brain" has become our team language. Or "oh don't worry, it's in the brain, I got it" It's been a wonder especially when engineers can reference.

Profilbild von Saman Ahmed

Saman Ahmedvor 2 Monaten

I've started treating my notes like product code, not docs. Every time I skip writing something down, I end up paying for it again a week later.

Profilbild von Noah Laker

Noah Lakervor 2 Monaten

Cute graphics but how does it actually improve your workflow

Profilbild von Curious Horizons

Curious Horizonsvor 2 Monaten

It's looks so complicated yet beautiful at the same time.. Fascinating tbh

Profilbild von unchosen.eth

unchosen.ethvor 2 Monaten

i like this approach

Profilbild von Roudy B 🇭🇹

Roudy B 🇭🇹vor 2 Monaten

Did it with Lenny’s archive. Most tokens I’ve ever spent but best thing I’ve ever built on my computer

Profilbild von Wemoo

Wemoovor 2 Monaten

the rulings note is the whole thing. tired of correcting the same tone issue in 6 different chats like it’s a new problem every time.

Profilbild von Arty

Artyvor 2 Monaten

Spot on. The real moat in 2026 isn't the model you call - it's the structured context you feed it. Having a single "rulings" file that acts as an evolving memory layer completely solves the infinite-feedback-loop problem. Pure genius workflow

Profilbild von StatysTheBaddest

StatysTheBaddestvor 2 Monaten

What?

Profilbild von Singulith

Singulithvor 2 Monaten

「知識」とは何か? 　それが具体的に定義されようとしている｡😃

Profilbild von ContextFirstAI

ContextFirstAIvor 2 Monaten

The tricky part isn't building the vault, it's keeping it trustworthy. Once it falls behind reality, every agent starts making the same wrong assumptions. How are you keeping the knowledge current as things change?

Profilbild von SD House Mafia

SD House Mafiavor 2 Monaten

Completely useless

Profilbild von AI Mastery Guide

AI Mastery Guidevor 2 Monaten

Fix a thing once instead of forever, that's such a clean system.

Profilbild von lunessa

lunessavor 2 Monaten

wait this vault setup is lowkey perfect for distributed computing too like handling all those massive data loads from the real world testing layers before a healthcare product even gets to the regulators. anyone else already trying this at that scale or is it just me??

Profilbild von Apollo Ridgeway

Apollo Ridgewayvor 2 Monaten

This is literally nothing

Profilbild von manikantaDasari 🇮🇳

manikantaDasari 🇮🇳vor 2 Monaten

Have you ever going consume the entire data. First do you know whats there in that ?

Profilbild von Goodness O. Omo-okoroh

Goodness O. Omo-okorohvor 2 Monaten

Definitely checking this out

Profilbild von Magicfit

Magicfitvor 2 Monaten

the vault is the actual moat

Profilbild von Pinkesh | SaaS MVPs in 2 Weeks

Pinkesh | SaaS MVPs in 2 Weeksvor 2 Monaten

the building part is easy tbh. keeping it fresh is what kills it. mine goes stale in like 2 weeks unless i force updates into the loop. how are you handling that part?

Profilbild von Max Bevza

Max Bevzavor 2 Monaten

this knowledge base meta is about to print

Profilbild von Gungun Pandey

Gungun Pandeyvor 2 Monaten

This is so cooool

Profilbild von Pixel

Pixelvor 2 Monaten

The vault becomes the actual business. The workers are just interchangeable hands))

Ähnliche Videos

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, signals, messages, metrics - one note per fact, 50-150 words, a title you can say out loud ("a budget that can survive"), four frontmatter keys (type, tags, created, status) - every note links to its folder hub, two siblings and one note in another folder, so the graph becomes one connected web instead of eleven islands - a rulings folder where every correction you give an agent becomes one dated line, and every run reads it before drafting... a correction becomes permanent instead of repeated - Claude Code pointed at the vault reads the hubs first, greps the rulings, then drafts, and everything it learns goes back in as a note the same day - graph view colored by folder, hubs in white, so you see which cluster is thin before a workflow fails the article below teaches you how to build the full workflow step-by-step:

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, signals, messages, metrics - one note per fact, 50-150 words, a title you can say out loud ("a budget that can survive"), four frontmatter keys (type, tags, created, status) - every note links to its folder hub, two siblings and one note in another folder, so the graph becomes one connected web instead of eleven islands - a rulings folder where every correction you give an agent becomes one dated line, and every run reads it before drafting... a correction becomes permanent instead of repeated - Claude Code pointed at the vault reads the hubs first, greps the rulings, then drafts, and everything it learns goes back in as a note the same day - graph view colored by folder, hubs in white, so you see which cluster is thin before a workflow fails the article below teaches you how to build the full workflow step-by-step:

Machina

30,551 Aufrufe • vor 1 Monat

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

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

Yarchi

58,643 Aufrufe • vor 4 Monaten

i simply can't get over how few people are actually doing this... Andrej Karpathy, co-founder of openai, basically described the whole setup and almost nobody built it let me break down what it actually does... every scattered note, every source you dumped somewhere and forgot, every pattern buried across hundreds of files... compiled once into something claude can scan in seconds instead of rereading cold every session 1. three folders, that's the whole vault: raw holds the originals untouched, wiki holds what claude compiles from them, instructions holds the rules for how it compiles 2. claude reads raw/ once, turns each source into linked wiki pages with sources cited, never opens the raw files again after that 3. every contradiction gets flagged right inside the wiki with both sides and dates, every future session reads the flag first, so you catch it once instead of forever the raw files are disposable... the wiki is what actually holds the value full breakdown is in the article below

i simply can't get over how few people are actually doing this... Andrej Karpathy, co-founder of openai, basically described the whole setup and almost nobody built it let me break down what it actually does... every scattered note, every source you dumped somewhere and forgot, every pattern buried across hundreds of files... compiled once into something claude can scan in seconds instead of rereading cold every session 1. three folders, that's the whole vault: raw holds the originals untouched, wiki holds what claude compiles from them, instructions holds the rules for how it compiles 2. claude reads raw/ once, turns each source into linked wiki pages with sources cited, never opens the raw files again after that 3. every contradiction gets flagged right inside the wiki with both sides and dates, every future session reads the flag first, so you catch it once instead of forever the raw files are disposable... the wiki is what actually holds the value full breakdown is in the article below

kai

34,911 Aufrufe • vor 2 Monaten

i genuinely can't understand why this isn't the first thing every claude user builds... andrej karpathy, co-founder of openai, quietly solved the exact problem making your ai useless and almost nobody noticed here's the problem he solved... every session claude starts from zero, rereads the same files, forgets every contradiction it already caught, burns tokens relearning what it knew yesterday, forever 1. raw holds the truth once, wiki holds the compiled answer forever, instructions hold the one rule that stops it from ever getting messy again 2. claude opens a raw file exactly one time in its entire life, after that it only speaks in wiki pages with the sources already cited 3. the moment claude catches you contradicting yourself, it writes both versions into the wiki with dates, so it never asks you the same wrong question twice your raw files are disposable... the compiled wiki is the only thing that actually compounds full breakdown is in the article below

i genuinely can't understand why this isn't the first thing every claude user builds... andrej karpathy, co-founder of openai, quietly solved the exact problem making your ai useless and almost nobody noticed here's the problem he solved... every session claude starts from zero, rereads the same files, forgets every contradiction it already caught, burns tokens relearning what it knew yesterday, forever 1. raw holds the truth once, wiki holds the compiled answer forever, instructions hold the one rule that stops it from ever getting messy again 2. claude opens a raw file exactly one time in its entire life, after that it only speaks in wiki pages with the sources already cited 3. the moment claude catches you contradicting yourself, it writes both versions into the wiki with dates, so it never asks you the same wrong question twice your raw files are disposable... the compiled wiki is the only thing that actually compounds full breakdown is in the article below

kai

379,491 Aufrufe • vor 2 Monaten

you wrote a long careful note so it would remember the thing properly the note is the part that does not load what loads at the start of every session is the index line, the one sentence summary, and only the first two hundred lines of it or the first twenty five kilobytes, whichever runs out first the topic files underneath are read on demand, which means only if something in that one line makes it go and open them i checked mine: thirty nine index lines loading every session, thirty nine topic files loading none of the time the detail you were careful about is not context it is a footnote your agent has to choose to open and the sentence you dashed off in three seconds is the whole memory

you wrote a long careful note so it would remember the thing properly the note is the part that does not load what loads at the start of every session is the index line, the one sentence summary, and only the first two hundred lines of it or the first twenty five kilobytes, whichever runs out first the topic files underneath are read on demand, which means only if something in that one line makes it go and open them i checked mine: thirty nine index lines loading every session, thirty nine topic files loading none of the time the detail you were careful about is not context it is a footnote your agent has to choose to open and the sentence you dashed off in three seconds is the whole memory

Lagosaur

28,369 Aufrufe • vor 1 Monat

Obsidian + Claude just killed the $35K/year ghostwriter Sounds exactly like you, every time Pulls every relevant note you ever captured Ships finished drafts in under 90 seconds Gets sharper every month, not flatter The 30-minute vault + the voice profile that makes the output indistinguishable from yours Set up the stack: Install Obsidian: → 5 folders (00 CAPTURE → 04 SYSTEM) CLAUDE.md in 04 SYSTEM → 10 of your best pieces + your no-go phrases Tag every note in 01 - ACTIVE with the content vertical it feeds Claude Desktop + Filesystem MCP → reads every note in the vault Output Generator prompt in 04 - SYSTEM/prompts/ → triggered on demand 03 - OUTPUT/ → every draft lands here, linked back to source notes First prompt to Claude: Read my voice profile in CLAUDE.md Read every note tagged with [topic] in 01 - ACTIVE Write a complete draft in my voice - sentence rhythm, idioms, no-go phrases respected Synthesize across notes, don't summarize each Surface 1 angle no individual note contains but the combination supports Save to 03 - OUTPUT/[date]-[topic].md After it works, tune: voice profile (sentence length, idioms, things you'd never say) topic tags (one cluster per vertical - AI, crypto, growth) the "what would my reader push back on?" prompt before publishing draft length per format (thread / essay / newsletter) the Connection Surface (find the angle nobody used yet) the kill list (phrases the ghostwriter is never allowed to write) The numbers: → 4,000 notes → 1 monthly publishable pipeline → 90 seconds from prompt to first draft → 1 voice profile = unlimited content in that voice → 10 source pieces are all you need to train it → Month 3: drafts indistinguishable from your own Full breakdown above 👇

ZEUS⚡️

16,167 Aufrufe • vor 4 Monaten

I BUILT GROK BOT SECOND BRAIN 26 agents, one core, running off a single rule my own memory never followed: capture everything, forget nothing, connect it before you even ask. A voice note on a coffee walk gets split into a task and an idea in under 6 seconds - the core already knows the difference between something you have to do and something you just thought of. An idea from three weeks ago gets linked to the one you just had, automatically, before you remember you'd had it the first time. That visual -the rotating profile, the 26 glowing lines firing out through the skull, each one labeled with the agent running it - isn't a rendered mockup. It's the actual runtime. Every line is a live agent doing its job in real time, right now, in your browser. This isn't a note app. Note apps hold what you give them. This is a nervous system for everything your brain was never built to hold onto in the first place. Full build - the 26 agents, how memory actually persists, what it costs to set one up for real - is in the article.

Aleiah

259,520 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!

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

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

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

Miraqle

41,307 Aufrufe • vor 3 Monaten

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

A PHD JUST EXPLAINED HOW TO BECOME IMMORTAL WITH FABLE + GOD-MODE SECOND BRAIN ASSISTANT. This was science fiction in February, BUT now it's a weekend setup: > step one: build the second brain: every note, every decision, every opinion, the raw material of how you actually think > step two: Fable 5 tunes your own agent against that vault, iterating until the answers start sounding like yours > step three: Fable interviews you, deeply. the questions pull out the thinking you never bothered to write down And the catch he's right about, that everyone will skip: if your vault is full of AI slop, you're not cloning yourself. you're cloning ChatGPT with your name on it. the training data has to be YOU, handwritten takes, real decisions, actual taste. That's the quiet flip nobody says out loud: everyone is scared AI will replace them. operators are building the replacement themselves and sending it to work. Step one is the whole foundation, and I broke it down in the article below: the vault structure, the Claude wiring, the exact prompts. P.S. send the article to your Claude and let it start interviewing you tonight. the clone is only as good as what you feed it.

A PHD JUST EXPLAINED HOW TO BECOME IMMORTAL WITH FABLE + GOD-MODE SECOND BRAIN ASSISTANT. This was science fiction in February, BUT now it's a weekend setup: > step one: build the second brain: every note, every decision, every opinion, the raw material of how you actually think > step two: Fable 5 tunes your own agent against that vault, iterating until the answers start sounding like yours > step three: Fable interviews you, deeply. the questions pull out the thinking you never bothered to write down And the catch he's right about, that everyone will skip: if your vault is full of AI slop, you're not cloning yourself. you're cloning ChatGPT with your name on it. the training data has to be YOU, handwritten takes, real decisions, actual taste. That's the quiet flip nobody says out loud: everyone is scared AI will replace them. operators are building the replacement themselves and sending it to work. Step one is the whole foundation, and I broke it down in the article below: the vault structure, the Claude wiring, the exact prompts. P.S. send the article to your Claude and let it start interviewing you tonight. the clone is only as good as what you feed it.

Miraqle

32,328 Aufrufe • vor 3 Monaten

STOP TREATING YOUR OBSIDIAN VAULT AS AI MEMORY. WITHOUT ONE ROUTING FILE, CLAUDE IS BURNING TOKENS ON NOISE YOU FORGOT YOU SAVED. a folder full of markdown does not make Claude smart. what makes it smart is what your agent can find without rereading the whole vault. storage: write → tag → graph → agent scans everything the model touches the entire vault, hallucinates half of it, forgets by the next session. memory: write → index → route → agent opens two files the model reads the index first, follows one path, answers with a link back to the note. i have rebuilt my Obsidian vault three times this year. the first two collapsed inside a month because Claude kept guessing which folder to open. the third one holds because the first thing i ship now is the routing file. Markdown, links, and the graph view are not what changed. what changed was a one-line description per folder, written for the agent, kept current, loaded before any retrieval call. if your agent still starts every session by scanning your whole vault, you are running storage. write the routing file today.

STOP TREATING YOUR OBSIDIAN VAULT AS AI MEMORY. WITHOUT ONE ROUTING FILE, CLAUDE IS BURNING TOKENS ON NOISE YOU FORGOT YOU SAVED. a folder full of markdown does not make Claude smart. what makes it smart is what your agent can find without rereading the whole vault. storage: write → tag → graph → agent scans everything the model touches the entire vault, hallucinates half of it, forgets by the next session. memory: write → index → route → agent opens two files the model reads the index first, follows one path, answers with a link back to the note. i have rebuilt my Obsidian vault three times this year. the first two collapsed inside a month because Claude kept guessing which folder to open. the third one holds because the first thing i ship now is the routing file. Markdown, links, and the graph view are not what changed. what changed was a one-line description per folder, written for the agent, kept current, loaded before any retrieval call. if your agent still starts every session by scanning your whole vault, you are running storage. write the routing file today.

kocer

17,240 Aufrufe • vor 1 Monat

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.

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

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

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

Spike 1%

58,428 Aufrufe • vor 2 Monaten

Most Obsidian daily note setups get abandoned by Week 3! Not because the person is undisciplined. Because the system cost more attention than it returned. This build flips the ratio. Claude generates the morning brief from your vault before you open the note. The One Thing section forces a single prioritization decision rather than a list. Captures require zero structure or filing. End of day takes five minutes. A CLAUDE.md that contains the honest version of how you actually work and what derails you. The architecture that produces better days is built around who you actually are. This is the setup right here, bookmark it now! Follow NeilXbt for more Obsidian and Claude builds that solve the week three abandonment problem every other system ignores.

Most Obsidian daily note setups get abandoned by Week 3! Not because the person is undisciplined. Because the system cost more attention than it returned. This build flips the ratio. Claude generates the morning brief from your vault before you open the note. The One Thing section forces a single prioritization decision rather than a list. Captures require zero structure or filing. End of day takes five minutes. A CLAUDE.md that contains the honest version of how you actually work and what derails you. The architecture that produces better days is built around who you actually are. This is the setup right here, bookmark it now! Follow NeilXbt for more Obsidian and Claude builds that solve the week three abandonment problem every other system ignores.

NeilXbt

29,601 Aufrufe • vor 4 Monaten

THIS IS ANDREJ KARPATHY'S OBSIDIAN VAULT : THE BRAIN ANTHROPIC JUST HIRED FOR MILLIONS This is every idea, every decision and every connection he's made over years of work, visualized in real time. Everything else gets lost. The pattern you noticed last March. The connection between two problems you solved a year apart. The idea that would've changed everything if you'd remembered it in the room. This system keeps all of it. Every note links to another. Every link becomes a path. Every path is a decision he can retrace in seconds while everyone else starts from zero. Thousands of nodes. Hundreds of live connections. Years of thinking that never decayed, never died in a Slack thread, never got buried in a meeting nobody remembers. The breakthroughs aren't luck. They're the system handing him back a link he made eighteen months ago and forgot he had. No team. No wiki. No standups. One person and a tool that remembers everything he can't. Most people open Obsidian and make three notes they never open again. He built an operating system for his own thinking. Anthropic just paid millions for the output - this is the machine that produced it.

THIS IS ANDREJ KARPATHY'S OBSIDIAN VAULT : THE BRAIN ANTHROPIC JUST HIRED FOR MILLIONS This is every idea, every decision and every connection he's made over years of work, visualized in real time. Everything else gets lost. The pattern you noticed last March. The connection between two problems you solved a year apart. The idea that would've changed everything if you'd remembered it in the room. This system keeps all of it. Every note links to another. Every link becomes a path. Every path is a decision he can retrace in seconds while everyone else starts from zero. Thousands of nodes. Hundreds of live connections. Years of thinking that never decayed, never died in a Slack thread, never got buried in a meeting nobody remembers. The breakthroughs aren't luck. They're the system handing him back a link he made eighteen months ago and forgot he had. No team. No wiki. No standups. One person and a tool that remembers everything he can't. Most people open Obsidian and make three notes they never open again. He built an operating system for his own thinking. Anthropic just paid millions for the output - this is the machine that produced it.

Avid

65,533 Aufrufe • vor 4 Monaten

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Spike 1%

18,223 Aufrufe • vor 2 Monaten

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

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

I just built a Brand Operating System inside Claude Cowork 🤯 A connected system of files that every skill automatically reads from, so your hook writer, brief generator, and script writer all speak in your exact brand voice. All inside Claude Cowork. Perfect for DTC brands and agencies tired of generic AI output that sounds like every other brand in their category. If you're opening a new Claude chat and re-explaining your brand, re-pasting your voice guidelines, and re-describing your customers every single time, a Brand OS fixes the entire loop: → Build 3 foundation files once per brand → Every skill you create reads from the Brand OS automatically → Hook writer pulls your voice + customer pain points → Brief generator pulls your positioning + angles → Script writer pulls the brief + brand DNA → Every output is calibrated to your brand on the first pass No re-briefing Claude on every chat. No editing for an hour to fix generic AI phrasing. No creative that sounds like it could belong to any brand. What you get in the playbook: → The exact Brand OS file structure I use → Templates for all 3 files you can fill in for any brand → The architecture that makes every Claude skill 10x sharper → The exact setup for agencies running a Brand OS per client For agencies: this is how you build a perfect, reusable knowledge base for every client on your roster. Set up the Brand OS once per client, and every campaign after that is already calibrated. I put together a full playbook with the file templates, the architecture, and the exact setup process so you can build your own Brand OS for your brand or your clients. Want it for free? > Like this post > Comment "OS" And I'll send it over (must be following so I can DM)

Mike Futia

30,334 Aufrufe • vor 6 Monaten