Loading video...

Video Failed to Load

Go Home

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Claude knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - claude pulls links,...

polydao's profile picture

Mr. Buzzoni

21,386 subscribers

134,992 views • 7 days ago •via X (Twitter)

Science & Technology
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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

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

Yarchi

58,186 views • 2 months 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
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 views • 1 month ago

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

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

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

Spike 1%

58,428 views • 29 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.
10:19

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

While AI timeline argues about loop engineering, a 20-year-old student in Shenzhen built the biggest loop anyone's aimed at money: 300 agents, one brain, $1,200 -> 395,000. Not a prompt. Not a bot. A loop that runs the whole job on its own - and never asks him a thing. No fund. No backers. Just a laptop, a dorm room, and a bet that a swarm beats a genius. His wallet: The smartest single model still works one step at a time. His loop moves in 300 directions at once - and never checks in with him. Claude Opus 4.8 runs the floor as the brain. 300 agents are the hands. One loop ties them together: > Decompose - Opus breaks the market into targets > Dispatch - 300 agents scatter across them at once > Execute - thousands of reads in a single pass, not one by one > Review - Opus grades every edge before a cent moves The hands find. The brain judges. The loop learns what failed and runs again, tighter each time. One daily loss cap, and it shuts itself down. It's not a bot you babysit. It's a loop that runs the whole desk. Everyone's just learning to run one loop. He runs 300 in one. The edge was never the genius model - it's the size of the loop, and the brain in charge of it. Save this - the full 300-agent loop is laid out above, start to finish. You'll want it when you build your own. 300 agents are looping right now, hunting the markets everyone skips. Two clicks and their trades land in your wallet too:
0:53

While AI timeline argues about loop engineering, a 20-year-old student in Shenzhen built the biggest loop anyone's aimed at money: 300 agents, one brain, $1,200 -> 395,000. Not a prompt. Not a bot. A loop that runs the whole job on its own - and never asks him a thing. No fund. No backers. Just a laptop, a dorm room, and a bet that a swarm beats a genius. His wallet: The smartest single model still works one step at a time. His loop moves in 300 directions at once - and never checks in with him. Claude Opus 4.8 runs the floor as the brain. 300 agents are the hands. One loop ties them together: > Decompose - Opus breaks the market into targets > Dispatch - 300 agents scatter across them at once > Execute - thousands of reads in a single pass, not one by one > Review - Opus grades every edge before a cent moves The hands find. The brain judges. The loop learns what failed and runs again, tighter each time. One daily loss cap, and it shuts itself down. It's not a bot you babysit. It's a loop that runs the whole desk. Everyone's just learning to run one loop. He runs 300 in one. The edge was never the genius model - it's the size of the loop, and the brain in charge of it. Save this - the full 300-agent loop is laid out above, start to finish. You'll want it when you build your own. 300 agents are looping right now, hunting the markets everyone skips. Two clicks and their trades land in your wallet too:

cvxv666

53,163 views • 1 month 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.
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 views • 1 month ago

the loop is not the whole agent it is only one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls iteration turns retries budgets stop conditions success checks stalled progress use durable execution when the run must survive crashes → GRAPH ENGINEERING controls structure nodes edges state branches checkpoints routing handoffs build stateful agents as explicit graphs → inspect the topology without putting a model in the loop → HARNESS ENGINEERING controls exposure tools permissions memory sandboxes evals traces humans isolate generated code from the host machine → test behavior before users ever see it → preserve one trace across every model step and tool call → without loop control it keeps running without graph structure the path stays invisible without harness control it can reach anything the loop runs inside the graph the graph runs inside the harness the model is only one component debug the layer that actually owns the failure save this then read the article below
0:20

the loop is not the whole agent it is only one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls iteration turns retries budgets stop conditions success checks stalled progress use durable execution when the run must survive crashes → GRAPH ENGINEERING controls structure nodes edges state branches checkpoints routing handoffs build stateful agents as explicit graphs → inspect the topology without putting a model in the loop → HARNESS ENGINEERING controls exposure tools permissions memory sandboxes evals traces humans isolate generated code from the host machine → test behavior before users ever see it → preserve one trace across every model step and tool call → without loop control it keeps running without graph structure the path stays invisible without harness control it can reach anything the loop runs inside the graph the graph runs inside the harness the model is only one component debug the layer that actually owns the failure save this then read the article below

rari

20,934 views • 14 days ago

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.
0:37

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

shmidt

16,085 views • 1 month ago

Knowledge management consultants charge thousands to build systems that fail for the same reason every time! They require someone to maintain them. This architecture requires nobody. One emoji reaction on a Slack message. n8n detecting the tag and triggering the downstream workflow. Claude extracting the insight, structuring it into a vault note, and writing connections to related knowledge. The structured artifact lands in a shared Obsidian vault of plain Markdown files readable by any tool without API integration or vendor lock-in. The hard-won operational insight that leaves with the person who found it now stays in the vault permanently. Bookmark this so you do not lose it! Follow NeilXbt for more n8n and Claude builds that solve the knowledge problem.
0:56

Knowledge management consultants charge thousands to build systems that fail for the same reason every time! They require someone to maintain them. This architecture requires nobody. One emoji reaction on a Slack message. n8n detecting the tag and triggering the downstream workflow. Claude extracting the insight, structuring it into a vault note, and writing connections to related knowledge. The structured artifact lands in a shared Obsidian vault of plain Markdown files readable by any tool without API integration or vendor lock-in. The hard-won operational insight that leaves with the person who found it now stays in the vault permanently. Bookmark this so you do not lose it! Follow NeilXbt for more n8n and Claude builds that solve the knowledge problem.

NeilXbt

14,798 views • 2 months ago

Anthropic engineer: "You're not supposed to prompt Claude. You're supposed to build a graph that runs itself." In 30 minutes she breaks down how Anthropic builds graphs that remember, learn from their mistakes, and get smarter with every run. The difference between an agent and a graph: one runs once, the other gets better every time. Watch it, then read the full guide on graph engineering below.
31:27

Anthropic engineer: "You're not supposed to prompt Claude. You're supposed to build a graph that runs itself." In 30 minutes she breaks down how Anthropic builds graphs that remember, learn from their mistakes, and get smarter with every run. The difference between an agent and a graph: one runs once, the other gets better every time. Watch it, then read the full guide on graph engineering below.

Mahax

287,182 views • 18 days ago

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.
0:30

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

10,776 views • 1 month 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👇
0:56

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

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

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

Miraqle

41,307 views • 1 month ago

Obsidian Bases are better than Notion databases. Most people never use them because they're too technical. This Claude skill changes this: Bases automatically aggregate notes from your vault into a structured table. I have dozens of bases; the one in the video replaces the reference manager, for instance. Problem: Most struggle with setting them up. There's now a skill built by one of the Obsidian developers that runs inside Claude. The skill scans your vault and automatically generates the base. The hardest Obsidian feature to learn. Solved with one sentence.
1:53

Obsidian Bases are better than Notion databases. Most people never use them because they're too technical. This Claude skill changes this: Bases automatically aggregate notes from your vault into a structured table. I have dozens of bases; the one in the video replaces the reference manager, for instance. Problem: Most struggle with setting them up. There's now a skill built by one of the Obsidian developers that runs inside Claude. The skill scans your vault and automatically generates the base. The hardest Obsidian feature to learn. Solved with one sentence.

Ilya Shabanov

34,406 views • 3 months ago

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

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

shmidt

57,347 views • 1 month ago

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

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

Yarchi

141,580 views • 1 month ago

Obsidian + Claude Code is how Andrej Karpathy turns 15 years of notes into a brain that works while he sleeps. The method behind it costs $0 and takes 5 minutes a day and it outlived every productivity app since 2011. Every idea, link, and half-thought gets appended to the top of a single note, with no sorting, no folders, no tags. Once a week he scrolls through, and anything that still matters gets copied back to the top. Weak ideas sink. Strong ideas resurface 5, 10, 20 times and by the 20th pass your brain has already wired them into everything else you know. Repetition as a filter. That's the whole system. Now the 2026 upgrade almost nobody is running: Drop that note into an Obsidian vault and open the folder with Claude Code not the chat app, the terminal agent that reads files. 3 commands change everything: read my last 30 days of notes and find the 3 ideas I keep circling without acting on link every note mentioning this project into a CLAUDE.md of what I actually believe about it draft this week's post from the idea that resurfaced most Claude Code doesn't search your vault it walks it, follows the wikilinks, and hands you the patterns you were too close to see. Karpathy method filters the signal, Obsidian stores it, Claude Code compounds it. One is a habit, one is a folder, one is $20 a month together they're the closest thing to a second brain that thinks back. Most people collect notes for 10 years and never read them once. His notes read him.
1:29

Obsidian + Claude Code is how Andrej Karpathy turns 15 years of notes into a brain that works while he sleeps. The method behind it costs $0 and takes 5 minutes a day and it outlived every productivity app since 2011. Every idea, link, and half-thought gets appended to the top of a single note, with no sorting, no folders, no tags. Once a week he scrolls through, and anything that still matters gets copied back to the top. Weak ideas sink. Strong ideas resurface 5, 10, 20 times and by the 20th pass your brain has already wired them into everything else you know. Repetition as a filter. That's the whole system. Now the 2026 upgrade almost nobody is running: Drop that note into an Obsidian vault and open the folder with Claude Code not the chat app, the terminal agent that reads files. 3 commands change everything: read my last 30 days of notes and find the 3 ideas I keep circling without acting on link every note mentioning this project into a CLAUDE.md of what I actually believe about it draft this week's post from the idea that resurfaced most Claude Code doesn't search your vault it walks it, follows the wikilinks, and hands you the patterns you were too close to see. Karpathy method filters the signal, Obsidian stores it, Claude Code compounds it. One is a habit, one is a folder, one is $20 a month together they're the closest thing to a second brain that thinks back. Most people collect notes for 10 years and never read them once. His notes read him.

Spike 1%

12,346 views • 29 days ago

This Obsidian and Claude architecture charges nothing and removes the maintenance entirely. Obsidian stores everything as plain Markdown files. Claude Code points at the vault directory. No API integrations. No paid connectors. No configuration beyond a folder path. The gap between project management systems that get abandoned the moment life gets busy and a system that maintains itself from the notes you were already writing is not discipline or organizational skill. It is the architecture described in this article, and the afternoon it takes to build five markdown components that never need a status update meeting again.
0:27

This Obsidian and Claude architecture charges nothing and removes the maintenance entirely. Obsidian stores everything as plain Markdown files. Claude Code points at the vault directory. No API integrations. No paid connectors. No configuration beyond a folder path. The gap between project management systems that get abandoned the moment life gets busy and a system that maintains itself from the notes you were already writing is not discipline or organizational skill. It is the architecture described in this article, and the afternoon it takes to build five markdown components that never need a status update meeting again.

NeilXbt

32,130 views • 2 months ago