正在加载视频...

视频加载失败

返回首页

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...

neil_xbt's profile picture

NeilXbt

16,448 subscribers

14,798 次观看 • 5 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

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 次观看 • 5 个月前

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

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

NeilXbt

29,601 次观看 • 5 个月前

Karpathy sketched the second brain. these 7 open-source repos already built it for Obsidian + Claude Code 250,000+ GitHub stars between them, and every one is free to clone sorted by stars: 1. graphify - 134k stars turns your codebase, docs, SQL schemas and PDFs into one knowledge graph you can query ↳ 2. Understand-Anything - 88k stars maps any codebase into an interactive knowledge graph you can click through ↳ 3. claude-obsidian - 15.8k stars a second brain that organizes itself: drop in a source, Claude Code files it ↳ 4. obsidian-second-brain - 4.9k stars long-term memory for Claude Code, stored as plain markdown in your vault ↳ 5. mcp-obsidian - 4.5k stars one MCP server and Claude can read, search and write your whole vault ↳ 6. claudesidian - 2.6k stars a starter vault designed around Claude Code from the first note ↳ 7. second-brain - 756 stars an Obsidian wiki the model keeps up to date, built on Karpathy's LLM Wiki pattern ↳ where to start: > your knowledge lives in code -> graphify > your knowledge lives in Obsidian -> claude-obsidian > you just want Claude to remember -> obsidian-second-brain > you live in Claude Desktop -> mcp-obsidian the skills that sit on top of all seven are in the full map below ↓
0:24

Karpathy sketched the second brain. these 7 open-source repos already built it for Obsidian + Claude Code 250,000+ GitHub stars between them, and every one is free to clone sorted by stars: 1. graphify - 134k stars turns your codebase, docs, SQL schemas and PDFs into one knowledge graph you can query ↳ 2. Understand-Anything - 88k stars maps any codebase into an interactive knowledge graph you can click through ↳ 3. claude-obsidian - 15.8k stars a second brain that organizes itself: drop in a source, Claude Code files it ↳ 4. obsidian-second-brain - 4.9k stars long-term memory for Claude Code, stored as plain markdown in your vault ↳ 5. mcp-obsidian - 4.5k stars one MCP server and Claude can read, search and write your whole vault ↳ 6. claudesidian - 2.6k stars a starter vault designed around Claude Code from the first note ↳ 7. second-brain - 756 stars an Obsidian wiki the model keeps up to date, built on Karpathy's LLM Wiki pattern ↳ where to start: > your knowledge lives in code -> graphify > your knowledge lives in Obsidian -> claude-obsidian > you just want Claude to remember -> obsidian-second-brain > you live in Claude Desktop -> mcp-obsidian the skills that sit on top of all seven are in the full map below ↓

Mr. Buzzoni

30,515 次观看 • 19 天前

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,730 次观看 • 5 个月前

CLAUDE CODE + OBSIDIAN = KARPATHY'S SECOND BRAIN, BUILT FROM 7 FREE PLUGINS Andrej Karpathy: "Obsidian is the IDE; the LLM is the programmer; the wiki is the codebase." these 7 free plugins put Claude Code on Opus 5.5 inside that IDE. 38,457 GitHub stars, and your Obsidian vault becomes a second brain that does the work sorted by stars: 1. claudian - 15,849 stars Claude Code or Codex inside your vault, which becomes the agent's working folder ↳ 2. obsidian-copilot - 7,912 stars OpenCode, Claude Code and Codex in one panel next to your notes ↳ 3. smart-connections - 5,527 stars related notes surface while you type, on a local model with no API key ↳ 4. obsidian-local-rest-api - 3,093 stars a REST API plus an MCP server, so Claude Desktop reads and writes your notes ↳ 5. obsidian-agent-client - 2,463 stars chat with Claude Code, Codex or Gemini CLI and @-mention any note ↳ 6. smart-composer - 2,332 stars a chat that knows your whole vault, with one-click edits ↳ 7. obsidian-yolo - 1,378 stars chat, writing, a knowledge base and agent orchestration in one place ↳ where to start: > already paying for Claude Code -> claudian > want linked notes for $0 -> smart-connections > living in Claude Desktop -> obsidian-local-rest-api the person whose notes an agent can read walks into every meeting already briefed, and that is the person who gets the raise Karpathy's method for running a vault with Claude is below ↓
0:24

CLAUDE CODE + OBSIDIAN = KARPATHY'S SECOND BRAIN, BUILT FROM 7 FREE PLUGINS Andrej Karpathy: "Obsidian is the IDE; the LLM is the programmer; the wiki is the codebase." these 7 free plugins put Claude Code on Opus 5.5 inside that IDE. 38,457 GitHub stars, and your Obsidian vault becomes a second brain that does the work sorted by stars: 1. claudian - 15,849 stars Claude Code or Codex inside your vault, which becomes the agent's working folder ↳ 2. obsidian-copilot - 7,912 stars OpenCode, Claude Code and Codex in one panel next to your notes ↳ 3. smart-connections - 5,527 stars related notes surface while you type, on a local model with no API key ↳ 4. obsidian-local-rest-api - 3,093 stars a REST API plus an MCP server, so Claude Desktop reads and writes your notes ↳ 5. obsidian-agent-client - 2,463 stars chat with Claude Code, Codex or Gemini CLI and @-mention any note ↳ 6. smart-composer - 2,332 stars a chat that knows your whole vault, with one-click edits ↳ 7. obsidian-yolo - 1,378 stars chat, writing, a knowledge base and agent orchestration in one place ↳ where to start: > already paying for Claude Code -> claudian > want linked notes for $0 -> smart-connections > living in Claude Desktop -> obsidian-local-rest-api the person whose notes an agent can read walks into every meeting already briefed, and that is the person who gets the raise Karpathy's method for running a vault with Claude is below ↓

Mr. Buzzoni

13,216 次观看 • 14 天前

Obsidian plus Hermes Agent equals a system that thinks, remembers, and runs your life. Works while you sleep. Vault holds the knowledge. Hermes reads it. Claude reasons across it. Outputs land back in the vault as new notes. Every morning brief grounded in your actual projects. Every inbox processed automatically. Every week synthesized without effort. The personal operating system that compounds forever. Read this and Bookmark it now.
0:43

Obsidian plus Hermes Agent equals a system that thinks, remembers, and runs your life. Works while you sleep. Vault holds the knowledge. Hermes reads it. Claude reasons across it. Outputs land back in the vault as new notes. Every morning brief grounded in your actual projects. Every inbox processed automatically. Every week synthesized without effort. The personal operating system that compounds forever. Read this and Bookmark it now.

CyrilXBT

43,403 次观看 • 5 个月前

I can’t f*cking believe people still aren’t using this: Obsidian’s own CEO and team open-sourced the tools that make Claude work inside your vault, and they’re all free -> obsidian skills (by kepano) Obsidian’s CEO teaches Claude to write real Obsidian files: Markdown with wikilinks, Bases and Canvas, plus the Obsidian CLI -> defuddle (by kepano) strips any web page down to clean Markdown, so Claude reads the article and not the sidebars, and burns fewer tokens doing it -> obsidian importer (by obsidianmd) moves your whole history from Notion, Evernote, Apple Notes, Roam, Bear and OneNote into Markdown, so your agent can finally read it -> obsidian help (by obsidianmd) the official Obsidian docs as plain Markdown with an AGENTS.md file, so your agent learns Obsidian from the source -> obsidian clipper (by obsidianmd) the official web clipper that saves any page straight into your vault pick one, install it tonight and your Claude writes real Obsidian files from the first prompt bookmark it before it gets buried
0:26

I can’t f*cking believe people still aren’t using this: Obsidian’s own CEO and team open-sourced the tools that make Claude work inside your vault, and they’re all free -> obsidian skills (by kepano) Obsidian’s CEO teaches Claude to write real Obsidian files: Markdown with wikilinks, Bases and Canvas, plus the Obsidian CLI -> defuddle (by kepano) strips any web page down to clean Markdown, so Claude reads the article and not the sidebars, and burns fewer tokens doing it -> obsidian importer (by obsidianmd) moves your whole history from Notion, Evernote, Apple Notes, Roam, Bear and OneNote into Markdown, so your agent can finally read it -> obsidian help (by obsidianmd) the official Obsidian docs as plain Markdown with an AGENTS.md file, so your agent learns Obsidian from the source -> obsidian clipper (by obsidianmd) the official web clipper that saves any page straight into your vault pick one, install it tonight and your Claude writes real Obsidian files from the first prompt bookmark it before it gets buried

Ryven

40,189 次观看 • 7 天前

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 次观看 • 4 个月前

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

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

Kanika

38,795 次观看 • 3 个月前

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.
0:22

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

Dan McAteer

175,308 次观看 • 4 个月前

MOST PEOPLE DOWNLOAD OBSIDIAN AND USE NOTION AGAIN BY WEEK THREE. Not because Obsidian is hard. Because nobody gave them the complete picture before they started building. This masterclass is that complete picture. Empty vault → a second brain that compounds every week. Philosophy. Architecture. Linking. Daily notes. Maps of Content. Claude integration. Automated workflows. And the daily practice that makes it actually stick. Everything in one guide. Read this and bookmark it now.
0:53

MOST PEOPLE DOWNLOAD OBSIDIAN AND USE NOTION AGAIN BY WEEK THREE. Not because Obsidian is hard. Because nobody gave them the complete picture before they started building. This masterclass is that complete picture. Empty vault → a second brain that compounds every week. Philosophy. Architecture. Linking. Daily notes. Maps of Content. Claude integration. Automated workflows. And the daily practice that makes it actually stick. Everything in one guide. Read this and bookmark it now.

CyrilXBT

31,274 次观看 • 5 个月前

5,000 notes in Obsidian and none of them producing anything Most notes never get used. Not because the information was not valuable. Because every note-taking system optimises for capturing and ignores using entirely. Someone built a five-workflow Obsidian system designed from the opposite end. The contribution rate compounds from the first processed note. Here is the full build nobody is talking about. AI IS TURNING OBSIDIAN INTO A KNOWLEDGE ENGINE. Not because it captures better. Because it retrieves better. The average person has valuable insights buried in thousands of notes they never revisit. Claude changes that. It finds forgotten connections. Surfaces relevant context. Builds decision briefs. Generates writing from accumulated knowledge. The result: Less searching. More thinking. The future of note-taking isn't saving information. It's activating it.
0:53

5,000 notes in Obsidian and none of them producing anything Most notes never get used. Not because the information was not valuable. Because every note-taking system optimises for capturing and ignores using entirely. Someone built a five-workflow Obsidian system designed from the opposite end. The contribution rate compounds from the first processed note. Here is the full build nobody is talking about. AI IS TURNING OBSIDIAN INTO A KNOWLEDGE ENGINE. Not because it captures better. Because it retrieves better. The average person has valuable insights buried in thousands of notes they never revisit. Claude changes that. It finds forgotten connections. Surfaces relevant context. Builds decision briefs. Generates writing from accumulated knowledge. The result: Less searching. More thinking. The future of note-taking isn't saving information. It's activating it.

Dami-Defi

70,601 次观看 • 5 个月前

this is f*cking insane. andrej karpathy: "the biggest regret of every engineer in my field right now is every AI conversation they never saved, and in 10 years the ones who started saving in 2024 will be running circles around the rest of us" andrej karpathy, co-founder of openai, pulled 16M views on one idea: stop using AI to write code, use it to build a second brain that remembers every article, pdf, transcript and conversation you ever fed it you point claude code at a folder, drop anything into it, and claude reads it, cross-links it with everything already there, and writes it into a living wiki. your knowledge finally compounds instead of leaking out of your head every friday the stack: → brew install obsidian, mkdir ~/vault, cd ~/vault → run claude in that folder and type "init a knowledge vault with CLAUDE.md as the rules, /raw for sources, /wiki for your pages" → drop any file into /raw (youtube transcript, meeting notes, 400-page pdf, screenshot of a tweet) and type "ingest" → claude writes a wiki page, links it to 5 existing ones automatically, updates CLAUDE.md with any new pattern it noticed about how you think → never open a blank claude chat again. every question goes through the vault, every answer cites your own sources with dates and links 5 minutes to set up. compounding knowledge from that evening forward the ugly part most will scroll past: in 10 years the engineers who started this in 2024 will remember every book, every podcast, every meeting with receipts. you will remember none of them. karpathy already picked which side he is on and you are still not on his full step-by-step is in the article below bookmark this before you waste another monday
0:21

this is f*cking insane. andrej karpathy: "the biggest regret of every engineer in my field right now is every AI conversation they never saved, and in 10 years the ones who started saving in 2024 will be running circles around the rest of us" andrej karpathy, co-founder of openai, pulled 16M views on one idea: stop using AI to write code, use it to build a second brain that remembers every article, pdf, transcript and conversation you ever fed it you point claude code at a folder, drop anything into it, and claude reads it, cross-links it with everything already there, and writes it into a living wiki. your knowledge finally compounds instead of leaking out of your head every friday the stack: → brew install obsidian, mkdir ~/vault, cd ~/vault → run claude in that folder and type "init a knowledge vault with CLAUDE.md as the rules, /raw for sources, /wiki for your pages" → drop any file into /raw (youtube transcript, meeting notes, 400-page pdf, screenshot of a tweet) and type "ingest" → claude writes a wiki page, links it to 5 existing ones automatically, updates CLAUDE.md with any new pattern it noticed about how you think → never open a blank claude chat again. every question goes through the vault, every answer cites your own sources with dates and links 5 minutes to set up. compounding knowledge from that evening forward the ugly part most will scroll past: in 10 years the engineers who started this in 2024 will remember every book, every podcast, every meeting with receipts. you will remember none of them. karpathy already picked which side he is on and you are still not on his full step-by-step is in the article below bookmark this before you waste another monday

mojesko

465,420 次观看 • 11 天前

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

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

Yarchi

32,594 次观看 • 4 个月前

Claude Code doesn't replace n8n. Here's one project built with both People think Claude Code replaces n8n. So here's one real project: a returns desk for a small online shop, built with both. Step 1: Claude Code builds the app. The owner says one sentence ("Build me a returns page"). Claude Code does three things: It reads CLAUDE.md, the shop's handbook of name, colours and rules, which loads every session. It pulls the refund-policy skill. Skills are loaded only when they're needed. It writes the code, hits an error, fixes it, and ships a real returns page. Step 2: n8n wires it into the business. Every return fires a webhook, and the same route runs every time: the label goes out through Gmail a row is added to the spreadsheet a note is posted in Slack the refund goes through Stripe when the parcel is scanned back in Every run is logged, and it runs 24/7. Step 3: a routine does the thinking. Every night at 11, a Claude Code routine runs in Anthropic's cloud with the laptop closed. It reads the day's returns, spots that 6 of 9 mention the same seam, and writes the owner a report. The handoffs: Claude Code wrote the n8n workflow, and n8n calls Claude when a return doesn't fit any route. Claude Code builds and thinks. n8n runs the same routes all day. Together they run the business. #claudecode #aiautomation #aiagent #n8n
2:31

Claude Code doesn't replace n8n. Here's one project built with both People think Claude Code replaces n8n. So here's one real project: a returns desk for a small online shop, built with both. Step 1: Claude Code builds the app. The owner says one sentence ("Build me a returns page"). Claude Code does three things: It reads CLAUDE.md, the shop's handbook of name, colours and rules, which loads every session. It pulls the refund-policy skill. Skills are loaded only when they're needed. It writes the code, hits an error, fixes it, and ships a real returns page. Step 2: n8n wires it into the business. Every return fires a webhook, and the same route runs every time: the label goes out through Gmail a row is added to the spreadsheet a note is posted in Slack the refund goes through Stripe when the parcel is scanned back in Every run is logged, and it runs 24/7. Step 3: a routine does the thinking. Every night at 11, a Claude Code routine runs in Anthropic's cloud with the laptop closed. It reads the day's returns, spots that 6 of 9 mention the same seam, and writes the owner a report. The handoffs: Claude Code wrote the n8n workflow, and n8n calls Claude when a return doesn't fit any route. Claude Code builds and thinks. n8n runs the same routes all day. Together they run the business. #claudecode #aiautomation #aiagent #n8n

Professor Glitch

10,200 次观看 • 1 个月前

You don't fully understand what this integration could turn into. Five skills. Created by the CEO of Obsidian. Released publicly. Free to add. He read it and thought about who would pay him to implement it for them. Law firms. Agencies. Medical practices. All have the same problem, knowledge that lives in someone's head until that person leaves. He builds the vault. Writes the files. Connects Claude. Delivers in three days. $2,200 once. $1,500 every month after. The pitch is one sentence: your new employee will read every process, every client file, and every decision made in the last three years before their first day. 6 clients. $9,000 a month. 10 hours of work a week. Five skills from the CEO. One business on top of them.
0:24

You don't fully understand what this integration could turn into. Five skills. Created by the CEO of Obsidian. Released publicly. Free to add. He read it and thought about who would pay him to implement it for them. Law firms. Agencies. Medical practices. All have the same problem, knowledge that lives in someone's head until that person leaves. He builds the vault. Writes the files. Connects Claude. Delivers in three days. $2,200 once. $1,500 every month after. The pitch is one sentence: your new employee will read every process, every client file, and every decision made in the last three years before their first day. 6 clients. $9,000 a month. 10 hours of work a week. Five skills from the CEO. One business on top of them.

Superior

28,320 次观看 • 4 个月前

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic
7:55

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic

Gbenga Akindolani |AI Engineer | Automation Expert

46,436 次观看 • 5 个月前

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, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order
0:24

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, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order

Mr. Buzzoni

137,517 次观看 • 3 个月前

It's f*cking wild how many people still build their Claude + Obsidian setup by hand, when Obsidian's CEO already open-sourced all the tools 1. obsidian skills · 51K stars by kepano, Obsidian's CEO. Claude stops writing broken Markdown and starts writing real Obsidian: wikilinks, Bases, Canvas, even the CLI 2. defuddle · 9.9K stars by kepano. Claude stops paying tokens for cookie banners, menus and comments. it gets the article and nothing else 3. obsidian clipper · 5.5K stars the official web clipper. one click and any page lands in your vault, ready for Claude 4. obsidian help · 1.9K stars the official docs as plain Markdown, AGENTS.md included. your agent learns Obsidian from the people who built it 5. obsidian importer · 1.7K stars your whole past life in 15 apps, from Notion to Evernote to Apple Notes, turned into Markdown Claude can actually read install one tonight and Claude stops guessing how Obsidian works from the very first prompt save it, your vault will thank you
0:25

It's f*cking wild how many people still build their Claude + Obsidian setup by hand, when Obsidian's CEO already open-sourced all the tools 1. obsidian skills · 51K stars by kepano, Obsidian's CEO. Claude stops writing broken Markdown and starts writing real Obsidian: wikilinks, Bases, Canvas, even the CLI 2. defuddle · 9.9K stars by kepano. Claude stops paying tokens for cookie banners, menus and comments. it gets the article and nothing else 3. obsidian clipper · 5.5K stars the official web clipper. one click and any page lands in your vault, ready for Claude 4. obsidian help · 1.9K stars the official docs as plain Markdown, AGENTS.md included. your agent learns Obsidian from the people who built it 5. obsidian importer · 1.7K stars your whole past life in 15 apps, from Notion to Evernote to Apple Notes, turned into Markdown Claude can actually read install one tonight and Claude stops guessing how Obsidian works from the very first prompt save it, your vault will thank you

Brucky

89,934 次观看 • 5 天前

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the loop keeps its state in the vault, so the chat window can close anytime everything Claude knows lives in a markdown file the loop: > capture - a thought lands in 00-inbox > context - Claude Opus 5.5 pulls the links, tags and neighbouring notes > draft - edits happen in a git worktree, the live vault stays untouched > review - a critic agent reads the diff before anything ships > commit - appended to the vault, nothing overwritten the key insight: frontmatter fields like supports, contradicts and supersedes act as graph edges. the note format is the write API start with a plain loop. it costs roughly 2-4x a single direct call upgrade to a full graph only when state has to outlive the session, several agents need to coordinate, or you need to explain what changed. that step can run 10-50x one review assistant went 55% -> 72% -> 84% by walking through these shapes in order worth stealing even if you never build a graph: the review step most vaults skip it and let Claude write straight into live notes the mistakes stack up for months before anyone notices put that gate in first
0:24

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the loop keeps its state in the vault, so the chat window can close anytime everything Claude knows lives in a markdown file the loop: > capture - a thought lands in 00-inbox > context - Claude Opus 5.5 pulls the links, tags and neighbouring notes > draft - edits happen in a git worktree, the live vault stays untouched > review - a critic agent reads the diff before anything ships > commit - appended to the vault, nothing overwritten the key insight: frontmatter fields like supports, contradicts and supersedes act as graph edges. the note format is the write API start with a plain loop. it costs roughly 2-4x a single direct call upgrade to a full graph only when state has to outlive the session, several agents need to coordinate, or you need to explain what changed. that step can run 10-50x one review assistant went 55% -> 72% -> 84% by walking through these shapes in order worth stealing even if you never build a graph: the review step most vaults skip it and let Claude write straight into live notes the mistakes stack up for months before anyone notices put that gate in first

Mr. Buzzoni

29,941 次观看 • 1 个月前