Loading video...

Video Failed to Load

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

Obsidian 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.show more

Spike 1%

4,130 subscribers

54,491 views • 4 days ago •via X (Twitter)

Science & Technology Education Finance

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Obsidian + method Karpathy + Claude Code = a quantum second brain that talks back. Most second brains are graveyards you clip 300 articles, tag 80 notes, build a graph that looks like a galaxy, then never open it again. Karpathy fix is stupid simple: 1 file, append only, new thought on top, review by scrolling no folders, no tags, no 40-minute “PKM setup” videos. The capture layer is 1 Obsidian vault with 1 file called stream md, where every idea, quote and link lands in under 10 seconds, because anything slower and you quit by day 4. Once a week Claude Code reads the whole vault from the terminal with 1 prompt “find the 5 ideas I keep circling without noticing” and sees patterns across 6 months you can’t hold in working memory. Instead of searching keywords you ask questions like “what did I think about agent pricing in March,” and Claude greps 4,000 notes and quotes your own words back with file paths. Then the vault becomes context drafting a post, a pitch or a spec, Claude pulls in your past thinking instead of generic internet mush, and your output starts sounding like you, compressed. The first week feels pointless at 20 notes, month 1 brings the first “wait, I already solved this” moment, by month 3 Claude connects 2 notes written 70 days apart and that connection becomes your best post of the year, by month 6 you stop asking Google things you already answered. The whole setup costs $0 in software and 1 evening. Notion sells you a workspace, Obsidian gives you files, Claude gives them a voice. Everyone rents a second brain this one lives on your disk and grows. You wrote the notes, and now something finally reads them.

Obsidian + method Karpathy + Claude Code = a quantum second brain that talks back. Most second brains are graveyards you clip 300 articles, tag 80 notes, build a graph that looks like a galaxy, then never open it again. Karpathy fix is stupid simple: 1 file, append only, new thought on top, review by scrolling no folders, no tags, no 40-minute “PKM setup” videos. The capture layer is 1 Obsidian vault with 1 file called stream md, where every idea, quote and link lands in under 10 seconds, because anything slower and you quit by day 4. Once a week Claude Code reads the whole vault from the terminal with 1 prompt “find the 5 ideas I keep circling without noticing” and sees patterns across 6 months you can’t hold in working memory. Instead of searching keywords you ask questions like “what did I think about agent pricing in March,” and Claude greps 4,000 notes and quotes your own words back with file paths. Then the vault becomes context drafting a post, a pitch or a spec, Claude pulls in your past thinking instead of generic internet mush, and your output starts sounding like you, compressed. The first week feels pointless at 20 notes, month 1 brings the first “wait, I already solved this” moment, by month 3 Claude connects 2 notes written 70 days apart and that connection becomes your best post of the year, by month 6 you stop asking Google things you already answered. The whole setup costs $0 in software and 1 evening. Notion sells you a workspace, Obsidian gives you files, Claude gives them a voice. Everyone rents a second brain this one lives on your disk and grows. You wrote the notes, and now something finally reads them.

West Lord

62,978 views • 6 days ago

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

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

Yarchi

58,186 views • 1 month ago

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

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

West Lord

32,731 views • 28 days ago

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.

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

105,293 views • 25 days ago

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.

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

336,969 views • 1 month ago

A 26-year-old plugged Claude Code into his Obsidian vault and the vault started working night shifts. 9,412 notes. 6 years of reading, ideas, half-dead projects. Dead weight until 3 weeks ago. He pointed Claude Code at the vault folder. No plugins. No API glue. The vault is just markdown files, and Claude Code reads files. That's the whole trick everyone misses. Now every night at 2 AM a cron job wakes Claude inside the vault: reads the 40 newest notes links them to old ones he forgot existed writes a daily brief called "what your brain missed" drafts 3 content ideas from collisions between notes Morning 1 it connected a 2021 note on Roman logistics with a 2026 note on AI agent routing. That collision became a post. 214,000 views. Morning 9 it found a SaaS idea buried in a book summary from 2022. He built the landing page the same day. 61 signups before dinner. Morning 17 it flagged that 3 of his abandoned drafts were the same idea written 3 times. He merged them. Best thing he's shipped this year. Cost: $0 in new tools. Obsidian is free. The vault was already there. 6 years he treated his second brain like a warehouse. Turns out it was an employee waiting for a boss.

A 26-year-old plugged Claude Code into his Obsidian vault and the vault started working night shifts. 9,412 notes. 6 years of reading, ideas, half-dead projects. Dead weight until 3 weeks ago. He pointed Claude Code at the vault folder. No plugins. No API glue. The vault is just markdown files, and Claude Code reads files. That's the whole trick everyone misses. Now every night at 2 AM a cron job wakes Claude inside the vault: reads the 40 newest notes links them to old ones he forgot existed writes a daily brief called "what your brain missed" drafts 3 content ideas from collisions between notes Morning 1 it connected a 2021 note on Roman logistics with a 2026 note on AI agent routing. That collision became a post. 214,000 views. Morning 9 it found a SaaS idea buried in a book summary from 2022. He built the landing page the same day. 61 signups before dinner. Morning 17 it flagged that 3 of his abandoned drafts were the same idea written 3 times. He merged them. Best thing he's shipped this year. Cost: $0 in new tools. Obsidian is free. The vault was already there. 6 years he treated his second brain like a warehouse. Turns out it was an employee waiting for a boss.

Spike 1%

136,903 views • 3 days ago

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

YanXbt

20,617 views • 1 month ago

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

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

Yarchi

140,729 views • 1 month ago

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

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

shmidt

57,347 views • 18 days ago

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.

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

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.

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

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

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

Yarchi

32,476 views • 1 month ago

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

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

Miraqle

15,128 views • 24 days ago

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 views • 28 days ago

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

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

Gipp 🦅

17,790 views • 16 days ago

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

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

Yarchi

55,345 views • 1 month ago

turned this into a web app you can use with your own obsidian vault! no install, just one html file: point it at your notes folder, it embeds everything with gemini, clusters by meaning, and renders the 3d network in your browser. available now for x/twitter subscribers <3

turned this into a web app you can use with your own obsidian vault! no install, just one html file: point it at your notes folder, it embeds everything with gemini, clusters by meaning, and renders the 3d network in your browser. available now for x/twitter subscribers <3

Kat ⊷ the Poet Engineer

105,960 views • 5 months ago

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.

Avid

467,826 views • 27 days ago

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.

Avid

35,283 views • 1 month ago

how to use obsidian + claude code to build a 24/7 personal operating system and build your startup: 1. write everything in markdown (daily notes, projects, beliefs, people, meetings) 2. link your notes together so they mirror how your brain actually thinks. 3. install obsidian cli so claude code can read your entire vault + the relationships. 4. stop reexplaining projects every session. use reference files instead. 5. build custom slash commands: /context → load your full life + work state /trace → see how an idea evolved over months /connect → bridge two domains you’ve been circling /ideas → generate startup ideas from your vault /graduate → promote daily thoughts into real assets 6. keep a strict rule: human writes the vault. agents read it, suggest, execute. 7. let claude aka clode surface patterns you’ve been unconsciously circling for years. 8. delegate from inside your notes. one sentence in obsidian → agent handles the rest. 9. treat writing as leverage.the more you write, the more context your agents have. 10. understand this:markdown files are the oxygen of llms. i really enjoyed seeing how to use obsidian thanks to internetVin vin uses ai like a thinking partner wired into his life’s work. 99.99% of people won’t do this because it requires reflection + setup. but once the vault exists, the agent stops being generic. it starts thinking in your voice. episode is live on The Startup Ideas Podcast (SIP) 🧃 (more there) this one is different. send this tweet to a friend. im still processing how game changer obsidian + claude code is, maybe you too watch

how to use obsidian + claude code to build a 24/7 personal operating system and build your startup: 1. write everything in markdown (daily notes, projects, beliefs, people, meetings) 2. link your notes together so they mirror how your brain actually thinks. 3. install obsidian cli so claude code can read your entire vault + the relationships. 4. stop reexplaining projects every session. use reference files instead. 5. build custom slash commands: /context → load your full life + work state /trace → see how an idea evolved over months /connect → bridge two domains you’ve been circling /ideas → generate startup ideas from your vault /graduate → promote daily thoughts into real assets 6. keep a strict rule: human writes the vault. agents read it, suggest, execute. 7. let claude aka clode surface patterns you’ve been unconsciously circling for years. 8. delegate from inside your notes. one sentence in obsidian → agent handles the rest. 9. treat writing as leverage.the more you write, the more context your agents have. 10. understand this:markdown files are the oxygen of llms. i really enjoyed seeing how to use obsidian thanks to internetVin vin uses ai like a thinking partner wired into his life’s work. 99.99% of people won’t do this because it requires reflection + setup. but once the vault exists, the agent stops being generic. it starts thinking in your voice. episode is live on The Startup Ideas Podcast (SIP) 🧃 (more there) this one is different. send this tweet to a friend. im still processing how game changer obsidian + claude code is, maybe you too watch

GREG ISENBERG

1,132,600 views • 5 months ago