Загрузка видео...

Не удалось загрузить видео

На главную

THE OBSIDIAN GRAPH IS NOT A PRETTY NOTE MAP, IT IS A SELF-MAINTAINING AI WIKI THAT CAN TURN 120 SAVED SOURCES INTO 700 LINKED PAGES WHILE YOU ONLY KEEP ADDING NEW MATERIAL 00:11 the graph opens and the trick becomes obvious: every dot is a saved idea, every cluster...

gippp69's profile picture

Gipp 🦅

7,432 subscribers

41,728 просмотров • 1 месяц назад •via X (Twitter)

ОбразованиеНаука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇
0:25

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇

Mr. Buzzoni

18,500 просмотров • 28 дней назад

This beginner guide to Karpathy's LLM Wiki is one of the most useful AI videos i've shared this year Karpathy's idea: instead of asking AI questions every time, make it build you a permanent knowledge base that grows smarter over time > drop your documents into a folder > Claude reads them and builds a structured wiki in Obsidian > every time you add a new source, Claude Sonnet updates existing pages and links new ideas > ask complex questions - Claude Opus answers from the organized wiki, not raw files it's like having a researcher who never forgets and connects dots across everything you've ever given it full setup guide is in the video above
14:21

This beginner guide to Karpathy's LLM Wiki is one of the most useful AI videos i've shared this year Karpathy's idea: instead of asking AI questions every time, make it build you a permanent knowledge base that grows smarter over time > drop your documents into a folder > Claude reads them and builds a structured wiki in Obsidian > every time you add a new source, Claude Sonnet updates existing pages and links new ideas > ask complex questions - Claude Opus answers from the organized wiki, not raw files it's like having a researcher who never forgets and connects dots across everything you've ever given it full setup guide is in the video above

Mr. Buzzoni

58,787 просмотров • 3 месяцев назад

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.
34:07

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.

West Lord

75,208 просмотров • 1 месяц назад

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

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

Miraqle

15,128 просмотров • 1 месяц назад

Claude Code + Obsidian + 1 free GitHub skill = unlimited memory. Almost nobody is running this yet. Here’s the problem nobody tells you. Claude forgets you. Every new chat starts at 0. You re explain your business, your projects, your style every single time. That tax is why most people never compound anything with AI. The fix is 1 skill. It’s called Obsidian Mind. It turns your Obsidian vault into Claude’s long term brain. 2,000 notes, 14 projects, every idea you’ve ever dumped Claude reads it live and writes back to it live. It stops being a chatbot. It becomes a second brain that builds. What it does: → Bridges Claude Code straight into your vault. → Pulls any note in real time no copy paste, no context limit. → Updates your vault as you work Claude writes its own memory. → Links everything into 1 graph Claude can navigate. Day 1: Claude knows your last 6 months. Week 2: it drafts off your own past notes. Week 4: it’s running plays you forgot you wrote down. The people making real money with AI right now aren’t smarter. They just stopped starting from 0 every morning. Setup takes 11 minutes. The skill is free. You’ll have a brain that never forgets.
0:34

Claude Code + Obsidian + 1 free GitHub skill = unlimited memory. Almost nobody is running this yet. Here’s the problem nobody tells you. Claude forgets you. Every new chat starts at 0. You re explain your business, your projects, your style every single time. That tax is why most people never compound anything with AI. The fix is 1 skill. It’s called Obsidian Mind. It turns your Obsidian vault into Claude’s long term brain. 2,000 notes, 14 projects, every idea you’ve ever dumped Claude reads it live and writes back to it live. It stops being a chatbot. It becomes a second brain that builds. What it does: → Bridges Claude Code straight into your vault. → Pulls any note in real time no copy paste, no context limit. → Updates your vault as you work Claude writes its own memory. → Links everything into 1 graph Claude can navigate. Day 1: Claude knows your last 6 months. Week 2: it drafts off your own past notes. Week 4: it’s running plays you forgot you wrote down. The people making real money with AI right now aren’t smarter. They just stopped starting from 0 every morning. Setup takes 11 minutes. The skill is free. You’ll have a brain that never forgets.

West Lord

108,158 просмотров • 1 месяц назад

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 просмотров • 1 месяц назад

Andrej Karpathy (co-founder of OpenAI, LLM Wiki pattern creator): "Obsidian is the IDE. The LLM is the programmer. The wiki is the codebase. knowledge compounds like interest when the AI owns the maintenance." Someone built the open-source implementation of that principle. 6,800 stars. MIT licensed. Two minutes to install. Here is what it actually does: → ingest: drop a source, Claude reads it, pulls out people and ideas, creates 8-15 linked pages automatically → batch ingest: parallel agents read an entire pile at once, then cross-reference everything → query: ask your brain anything, it reads the cache, scans the index, cites the exact pages → /autoresearch: three rounds of search, fetch, synthesize, file — autonomous web research → lint: finds orphans, dead links, stale claims, missing cross-references → the real unlock: point every claude code project at the same vault — one brain, every project hot cache refreshed at the end of every session. next session opens with full recent context. no recap, no re-explaining. plain markdown, no subscription, no lock-in. Bookmark so you do not lose it! Follow NeilXbt for more Obsidian and Claude builds that show you what a self-maintaining second brain actually requires.
4:19

Andrej Karpathy (co-founder of OpenAI, LLM Wiki pattern creator): "Obsidian is the IDE. The LLM is the programmer. The wiki is the codebase. knowledge compounds like interest when the AI owns the maintenance." Someone built the open-source implementation of that principle. 6,800 stars. MIT licensed. Two minutes to install. Here is what it actually does: → ingest: drop a source, Claude reads it, pulls out people and ideas, creates 8-15 linked pages automatically → batch ingest: parallel agents read an entire pile at once, then cross-reference everything → query: ask your brain anything, it reads the cache, scans the index, cites the exact pages → /autoresearch: three rounds of search, fetch, synthesize, file — autonomous web research → lint: finds orphans, dead links, stale claims, missing cross-references → the real unlock: point every claude code project at the same vault — one brain, every project hot cache refreshed at the end of every session. next session opens with full recent context. no recap, no re-explaining. plain markdown, no subscription, no lock-in. Bookmark so you do not lose it! Follow NeilXbt for more Obsidian and Claude builds that show you what a self-maintaining second brain actually requires.

NeilXbt

33,993 просмотров • 1 месяц назад

i keep telling people to build this and they nod politely and never do it... andrej karpathy posted how to fix this a while ago, and everyone just keeps working the old way the dumb thing is this... you pay to teach claude the same lessons over and over, every chat is a fresh amnesia patient, every contradiction it catches evaporates the second you close the tab, and you accept this like it's just how ai works 1. one folder is a graveyard for originals that nobody edits, another folder is claude's active memory that only claude writes to, a third folder is a two-page rulebook that keeps claude from confusing them 2. a raw file gets read the day it arrives and then it's done, claude never touches it again, everything it needed is already extracted into wiki pages with the source cited right there 3. every time claude notices your new answer clashes with your old one, it doesn't pick a side, it writes both with dates, and from then on it treats you like someone who might be wrong the raw folder is a museum... the wiki is the actual working brain full breakdown is in the article below
0:20

i keep telling people to build this and they nod politely and never do it... andrej karpathy posted how to fix this a while ago, and everyone just keeps working the old way the dumb thing is this... you pay to teach claude the same lessons over and over, every chat is a fresh amnesia patient, every contradiction it catches evaporates the second you close the tab, and you accept this like it's just how ai works 1. one folder is a graveyard for originals that nobody edits, another folder is claude's active memory that only claude writes to, a third folder is a two-page rulebook that keeps claude from confusing them 2. a raw file gets read the day it arrives and then it's done, claude never touches it again, everything it needed is already extracted into wiki pages with the source cited right there 3. every time claude notices your new answer clashes with your old one, it doesn't pick a side, it writes both with dates, and from then on it treats you like someone who might be wrong the raw folder is a museum... the wiki is the actual working brain full breakdown is in the article below

kai

31,409 просмотров • 13 дней назад

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,253 просмотров • 2 месяцев назад

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 просмотров • 1 месяц назад

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
0:21

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 просмотров • 8 дней назад

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

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

Yarchi

55,345 просмотров • 2 месяцев назад

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇
14:28

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,734 просмотров • 2 месяцев назад

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.
4:19

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 просмотров • 1 месяц назад

🚨 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 просмотров • 10 дней назад

THIS GUY BUILT A BUSINESS SECOND BRAIN WITH CLAUDE CODE + OBSIDIAN IN 3 STEPS Most teams do not need another Notion workspace. They need a place where the company can remember how it works. The video shows a simple setup: 1. Create one empty folder called second brain. 2. Split it into 3 buckets: raw new knowledge wiki 3. Let Claude Code turn messy company material into connected notes. The useful part is the separation. Raw is where your existing stuff goes: SOPs, sales docs, process notes, client delivery checklists, old Loom summaries, onboarding docs. New knowledge is where fresh outside material lands: articles, clips, tactics, examples, market notes. Wiki is the cleaned version: concepts, roles, processes, SOPs, gaps, reusable decisions. That is where Claude Code becomes more useful than a normal chat window. Instead of asking it to remember random context forever, you give it a folder it can read, edit, and reorganize. Then Obsidian becomes the human interface. The Obsidian Web Clipper captures useful pages into the vault. Claude Code ingests them. The wiki gets updated. Then you can ask questions like: “Does my current workflow actually hold up?” That is the real point. Not “AI notes.” A business memory system that can compare what you do today against new information tomorrow. The caveat: this is not magic company intelligence. If your raw docs are vague, outdated, or full of tribal knowledge, Claude will organize weak inputs into cleaner weak outputs. You still need naming rules, review habits, and someone responsible for deleting junk. But the setup is refreshingly practical. Folder first. Clipper second. Claude Code as the maintainer. No giant knowledge base migration. No complex setup. Just a local vault that can slowly turn scattered business memory into something searchable, editable, and actually reusable.
1:25

THIS GUY BUILT A BUSINESS SECOND BRAIN WITH CLAUDE CODE + OBSIDIAN IN 3 STEPS Most teams do not need another Notion workspace. They need a place where the company can remember how it works. The video shows a simple setup: 1. Create one empty folder called second brain. 2. Split it into 3 buckets: raw new knowledge wiki 3. Let Claude Code turn messy company material into connected notes. The useful part is the separation. Raw is where your existing stuff goes: SOPs, sales docs, process notes, client delivery checklists, old Loom summaries, onboarding docs. New knowledge is where fresh outside material lands: articles, clips, tactics, examples, market notes. Wiki is the cleaned version: concepts, roles, processes, SOPs, gaps, reusable decisions. That is where Claude Code becomes more useful than a normal chat window. Instead of asking it to remember random context forever, you give it a folder it can read, edit, and reorganize. Then Obsidian becomes the human interface. The Obsidian Web Clipper captures useful pages into the vault. Claude Code ingests them. The wiki gets updated. Then you can ask questions like: “Does my current workflow actually hold up?” That is the real point. Not “AI notes.” A business memory system that can compare what you do today against new information tomorrow. The caveat: this is not magic company intelligence. If your raw docs are vague, outdated, or full of tribal knowledge, Claude will organize weak inputs into cleaner weak outputs. You still need naming rules, review habits, and someone responsible for deleting junk. But the setup is refreshingly practical. Folder first. Clipper second. Claude Code as the maintainer. No giant knowledge base migration. No complex setup. Just a local vault that can slowly turn scattered business memory into something searchable, editable, and actually reusable.

kocer

16,642 просмотров • 1 месяц назад

Fable 5 and Karpathy's knowledge base trick are basically a cheat code. Someone just dropped a full walkthrough on building the most powerful second brain ever Andrej Karpathy shared a simple idea: use an LLM to build personal knowledge bases. Index your sources, let the model organize them, and use Obsidian as the front end. Someone just built the full thing with Claude Code and Fable 5, and walked through every step You drop your sources into a folder (YouTube transcripts, PDFs, articles, meeting notes) and Claude Code reads them, splits them into linked wiki pages, and builds a living second brain that connects everything. It grows on its own as you add more. Where Fable 5 pulls ahead: it found a connection buried across two sources you'd miss reading them separately. And asked to turn the messy web of links into something a beginner could understand, it produced clean, simple HTML in one shot. The same task took a full day on Opus 4.8 and came out worse. The best part: it's all just markdown files with routing. So it's not locked to Claude Code. Plug it into Codex or any agent you want. Give your AI a real knowledge base, and it stops guessing and starts knowing. Bookmark this.
14:34

Fable 5 and Karpathy's knowledge base trick are basically a cheat code. Someone just dropped a full walkthrough on building the most powerful second brain ever Andrej Karpathy shared a simple idea: use an LLM to build personal knowledge bases. Index your sources, let the model organize them, and use Obsidian as the front end. Someone just built the full thing with Claude Code and Fable 5, and walked through every step You drop your sources into a folder (YouTube transcripts, PDFs, articles, meeting notes) and Claude Code reads them, splits them into linked wiki pages, and builds a living second brain that connects everything. It grows on its own as you add more. Where Fable 5 pulls ahead: it found a connection buried across two sources you'd miss reading them separately. And asked to turn the messy web of links into something a beginner could understand, it produced clean, simple HTML in one shot. The same task took a full day on Opus 4.8 and came out worse. The best part: it's all just markdown files with routing. So it's not locked to Claude Code. Plug it into Codex or any agent you want. Give your AI a real knowledge base, and it stops guessing and starts knowing. Bookmark this.

Shadow Nick

47,058 просмотров • 1 месяц назад

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 просмотров • 1 месяц назад

Prompt engineering is where people go when they refuse to write files Karpathy's LLM Wiki gist is painfully simple: > raw sources stay untouched > the agent writes the wiki > `CLAUDE.md` or `AGENTS.md` tells it the rules > `index.md` maps the pages > `log.md` records what changed That is why a good answer should not die in chat history If the model gives you a useful comparison, summary, decision, bug explanation, or research thread, file it back into the project Use: > `wiki/topics/[topic].md` > `wiki/entities/[person-or-company].md` > `wiki/sources/[source-name].md` > `wiki/analysis/[question].md` Make the agent keep the wiki from rotting: > backlinks > summaries > contradictions > stale claims > orphan pages > missing source links For coding projects, same idea: > `CLAUDE.md`: who you are, project rules, files not to touch > `index.md`: current files and features > `log.md`: date, change, reason > saved pages: decisions you do not want to re-explain Start by saving one good answer today
11:03

Prompt engineering is where people go when they refuse to write files Karpathy's LLM Wiki gist is painfully simple: > raw sources stay untouched > the agent writes the wiki > `CLAUDE.md` or `AGENTS.md` tells it the rules > `index.md` maps the pages > `log.md` records what changed That is why a good answer should not die in chat history If the model gives you a useful comparison, summary, decision, bug explanation, or research thread, file it back into the project Use: > `wiki/topics/[topic].md` > `wiki/entities/[person-or-company].md` > `wiki/sources/[source-name].md` > `wiki/analysis/[question].md` Make the agent keep the wiki from rotting: > backlinks > summaries > contradictions > stale claims > orphan pages > missing source links For coding projects, same idea: > `CLAUDE.md`: who you are, project rules, files not to touch > `index.md`: current files and features > `log.md`: date, change, reason > saved pages: decisions you do not want to re-explain Start by saving one good answer today

Alpha Batcher

14,041 просмотров • 2 месяцев назад

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,476 просмотров • 1 месяц назад