Loading video...

Video Failed to Load

Go Home

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

undefinedKi's profile picture

Yarchi

9,886 subscribers

138,564 views • 17 days ago •via X (Twitter)

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

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

Yarchi

55,345 views • 27 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.
0:42

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Avid

334,862 views • 24 days ago

Obsidian + Claude Code builds a real second brain in 17 minutes. Claude Code reads entire vault, connects notes & builds a knowledge graph of everything you've ever written. Bookmark it. This one actually works.
17:08

Obsidian + Claude Code builds a real second brain in 17 minutes. Claude Code reads entire vault, connects notes & builds a knowledge graph of everything you've ever written. Bookmark it. This one actually works.

0xMarioNawfal

68,173 views • 2 months ago

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.
1:48

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

CyrilXBT

318,620 views • 13 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.
0:34

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

West Lord

102,324 views • 9 days ago

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

172,023 views • 17 days 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.
1:57

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,401 views • 12 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
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

57,975 views • 1 month ago

everyone's talking about building a second brain with claude code + obsidian right now. so i made a full video walkthrough showing exactly how to set it up from scratch. drop an article into a folder. claude code reads it, creates wiki pages, builds relationships between concepts, and links everything automatically. by 20 sources your wiki knows more about your domain than you can hold in your head. here's the full setup:
13:22

everyone's talking about building a second brain with claude code + obsidian right now. so i made a full video walkthrough showing exactly how to set it up from scratch. drop an article into a folder. claude code reads it, creates wiki pages, builds relationships between concepts, and links everything automatically. by 20 sources your wiki knows more about your domain than you can hold in your head. here's the full setup:

J.B.

54,534 views • 2 months ago

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

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

Shadow Nick

45,330 views • 3 days ago

holy shit.. you can install claude code in 2 minutes and automate your entire polymarket strategy buy claude pro ($20) install: windows: winget install Anthropic.ClaudeCode mac: brew install claude authorize: run claude → oauth login → done navigate to folder: cd ~/polymarket-bot run claude paste one prompt and it builds everything ⭣
0:26

holy shit.. you can install claude code in 2 minutes and automate your entire polymarket strategy buy claude pro ($20) install: windows: winget install Anthropic.ClaudeCode mac: brew install claude authorize: run claude → oauth login → done navigate to folder: cd ~/polymarket-bot run claude paste one prompt and it builds everything ⭣

Phosphen

36,418 views • 5 months ago

Claude Code feels completely different once you install this. Anthropic quietly released an official plugin called claude-code-setup and it basically turns Claude Code from “pretty good” into an actual AI dev environment. It scans your project and recommends: → hooks → skills → MCP servers → subagents → automations Then sets everything up step-by-step for you. Most people are using Claude Code completely vanilla… which is why their experience feels messy. The real power comes from the ecosystem around it. Install: /plugin install claude-code-setup@claude-plugins-official Bookmark this before you forget it.
0:26

Claude Code feels completely different once you install this. Anthropic quietly released an official plugin called claude-code-setup and it basically turns Claude Code from “pretty good” into an actual AI dev environment. It scans your project and recommends: → hooks → skills → MCP servers → subagents → automations Then sets everything up step-by-step for you. Most people are using Claude Code completely vanilla… which is why their experience feels messy. The real power comes from the ecosystem around it. Install: /plugin install claude-code-setup@claude-plugins-official Bookmark this before you forget it.

Radha Tripathi

75,081 views • 1 month ago

Claude Code is now free to run. Most people still think you need a paid setup. Here’s the basic flow: → Install Claude Code with the official installer. → Create a free OpenRouter account. → Grab your API key. → Install Claude Code Router. → Point Claude Code to the local router. → Choose a free model with the :free suffix. → Run CCR code instead of normal Claude Code. → Check /status to confirm it works. You keep the Claude Code workflow. You just route it through a free model.
9:31

Claude Code is now free to run. Most people still think you need a paid setup. Here’s the basic flow: → Install Claude Code with the official installer. → Create a free OpenRouter account. → Grab your API key. → Install Claude Code Router. → Point Claude Code to the local router. → Choose a free model with the :free suffix. → Run CCR code instead of normal Claude Code. → Check /status to confirm it works. You keep the Claude Code workflow. You just route it through a free model.

Julian Goldie SEO

17,618 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,444 views • 12 days ago

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

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

NeilXbt

33,993 views • 8 days ago

INSTEAD OF WATCHING NETFLIX TONIGHT. Spend 1 hour with this. How To Build The Ultimate Ai Second Brain (Obsidian + Claude Code ) The people who watch this tonight will wake up tomorrow with a new skill. Watch it and Bookmark it now.
58:33

INSTEAD OF WATCHING NETFLIX TONIGHT. Spend 1 hour with this. How To Build The Ultimate Ai Second Brain (Obsidian + Claude Code ) The people who watch this tonight will wake up tomorrow with a new skill. Watch it and Bookmark it now.

AilaunchX

17,830 views • 1 month ago

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

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

Mr. Buzzoni

58,787 views • 1 month ago

🆕 Make Claude Code deploy what it builds locally to Railway 1. Install the Railway Agent skill 2. That's it. Claude Code figures out the rest
6:02

🆕 Make Claude Code deploy what it builds locally to Railway 1. Install the Railway Agent skill 2. That's it. Claude Code figures out the rest

Railway

26,754 views • 4 months ago

Noah Brier (Noah Brier) uses Claude Code as his second brain—it’s the coolest notetaking setup I’ve ever seen. He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian (Obsidian) vault. He does it all from his phone. I had him on the show to tell us exactly how he’s pulling this off. We get into: - The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates. - The “thinking partner” that lives inside Noah’s second brain: Noah points out that in the hype around AI’s ability to write, the fact that it can read is overlooked. That’s why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away. - How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works. This episode of Every 📧’s AI & I is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain. Watch below! Timestamps: Introduction: 00:01:19 How you can do deep work on your phone: 00:04:28 Why Noah thinks Grok has the best voice AI: 00:06:14 The nuts and bolts of Noah’s Claude Code-Obsidian setup: 00:11:39 Using an agent in Claude Code as a “thinking partner”: 00:23:59 Noah’s Thomas’ English Muffin theory of AI: 00:35:07 The white space still left to explore in AI: 00:44:04 How Noah is preparing his kids for AI: 00:50:41 How he brought his Claude Code setup to mobile: 01:01:54
1:11:52

Noah Brier (Noah Brier) uses Claude Code as his second brain—it’s the coolest notetaking setup I’ve ever seen. He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian (Obsidian) vault. He does it all from his phone. I had him on the show to tell us exactly how he’s pulling this off. We get into: - The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates. - The “thinking partner” that lives inside Noah’s second brain: Noah points out that in the hype around AI’s ability to write, the fact that it can read is overlooked. That’s why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away. - How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works. This episode of Every 📧’s AI & I is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain. Watch below! Timestamps: Introduction: 00:01:19 How you can do deep work on your phone: 00:04:28 Why Noah thinks Grok has the best voice AI: 00:06:14 The nuts and bolts of Noah’s Claude Code-Obsidian setup: 00:11:39 Using an agent in Claude Code as a “thinking partner”: 00:23:59 Noah’s Thomas’ English Muffin theory of AI: 00:35:07 The white space still left to explore in AI: 00:44:04 How Noah is preparing his kids for AI: 00:50:41 How he brought his Claude Code setup to mobile: 01:01:54

Dan Shipper 📧

30,792 views • 10 months ago

Claude finally killed the need for OpenClaw They launched "Claude Channels" which allows you to control Claude Code from your Telegram / Discord I show you how to set it up in ~6 minutes in mainly 3 steps Step 1: Create bot with BotFather Step 2: Install the Claude plugin Step 3: Pair with a code Now I can code, research, manage files from my phone using Claude Code If you don't watch this tutorial now I highly suggest you bookmark for later!
6:22

Claude finally killed the need for OpenClaw They launched "Claude Channels" which allows you to control Claude Code from your Telegram / Discord I show you how to set it up in ~6 minutes in mainly 3 steps Step 1: Create bot with BotFather Step 2: Install the Claude plugin Step 3: Pair with a code Now I can code, research, manage files from my phone using Claude Code If you don't watch this tutorial now I highly suggest you bookmark for later!

Chris ☕️

70,187 views • 3 months ago