正在加载视频...

视频加载失败

返回首页

Someone projected their entire Obsidian vault into 3D and the shape revealed where they think and where they don't This is the work of Blake Crosley, "Topologies of Thought: Obsidian in Embedding Space," building on the three topologies Kat (Kat ⊷ the Poet Engineer ) first explored. Take 15,800...

undefinedKi's profile picture

Yarchi

15,572 subscribers

14,353 次观看 • 3 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

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

相关视频

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.
0:55

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Spike 1%

18,223 次观看 • 2 个月前

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

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

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

Kat ⊷ the Poet Engineer

106,855 次观看 • 7 个月前

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.
0:23

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.

Simplifying AI

68,025 次观看 • 1 个月前

THIS GUY BUILT A CLAUDE CODE X OBSIDIAN MAP OF HIS ENTIRE CONTENT SYSTEM This is the useful version of “AI second brain.” Not dumping more notes. Not asking Claude for a prettier folder system. Not making a canvas because it looks smart. In the video, he points Claude Code at his Obsidian setup and shows a visual map of the actual content pipeline: Analysis Ideation Prep Scripting Prep Performance The interesting part is the shape. Each stage is connected to the next one. Some boxes show sub-processes. One section shows a router detecting content type and routing a short into the next step. There are references attached to the flow. That is a real payoff: you stop treating your vault like storage and start treating it like an inspectable machine. The move is simple: 1. Put the real workflow in markdown 2. Let Claude Code inspect the vault 3. Ask it to find stages, dependencies, and missing links 4. Turn the output into an Obsidian map 5. Use the map to see what is manual, duplicated, or broken This works because Claude Code is not just summarizing a note. It can read across prompts, docs, scripts, references, and messy process files, then expose the structure you stopped seeing. That is why the demo hits. The video is not really about “better note-taking.” It is about making your private operating system visible enough to debug. Caveat: a beautiful graph does not mean you have a working system. If the notes are vague, the map will be vague. If the process is fake, Claude will draw a fake process very cleanly. If nothing feeds back into performance, the canvas is just decoration. But if the vault already contains real work, Claude Code x Obsidian becomes a powerful audit tool. Your notes stop being a pile. They become a map of what you actually do.
0:20

THIS GUY BUILT A CLAUDE CODE X OBSIDIAN MAP OF HIS ENTIRE CONTENT SYSTEM This is the useful version of “AI second brain.” Not dumping more notes. Not asking Claude for a prettier folder system. Not making a canvas because it looks smart. In the video, he points Claude Code at his Obsidian setup and shows a visual map of the actual content pipeline: Analysis Ideation Prep Scripting Prep Performance The interesting part is the shape. Each stage is connected to the next one. Some boxes show sub-processes. One section shows a router detecting content type and routing a short into the next step. There are references attached to the flow. That is a real payoff: you stop treating your vault like storage and start treating it like an inspectable machine. The move is simple: 1. Put the real workflow in markdown 2. Let Claude Code inspect the vault 3. Ask it to find stages, dependencies, and missing links 4. Turn the output into an Obsidian map 5. Use the map to see what is manual, duplicated, or broken This works because Claude Code is not just summarizing a note. It can read across prompts, docs, scripts, references, and messy process files, then expose the structure you stopped seeing. That is why the demo hits. The video is not really about “better note-taking.” It is about making your private operating system visible enough to debug. Caveat: a beautiful graph does not mean you have a working system. If the notes are vague, the map will be vague. If the process is fake, Claude will draw a fake process very cleanly. If nothing feeds back into performance, the canvas is just decoration. But if the vault already contains real work, Claude Code x Obsidian becomes a powerful audit tool. Your notes stop being a pile. They become a map of what you actually do.

kocer

15,941 次观看 • 2 个月前

Andrej Karpathy keeps his entire second brain in Obsidian 1 folder of plain text files, nothing else. Here’s the exact setup, free, that turns 1 vault into a brain you can actually query. Why most “second brains” die: Notion is a database you forget to open, ChatGPT memory wipes itself after 30 messages, and both lock your notes inside their cloud. Karpathy rule is the opposite: your notes are the 1 dataset nobody else on earth has, so keep them in plain markdown, own them forever, and let the AI read them later. 3 phases. Phase 1 — Capture with 0 friction. Install Obsidian free, local, 1 hotkey to a daily note. Dump everything into it: ideas, links, quotes, 2-line thoughts, no folders, no tags, no system. Target is 5 notes a day. Phase 2 — Let the graph connect itself. Install Smart Connections and it runs embeddings on every note you’ve ever written, so 2 notes you wrote 4 months apart and never linked by hand suddenly surface as neighbors. That’s the fireworks in the 3D graph each burst is a cluster of ideas your brain forgot it owned. Phase 3 — Query your brain. Point Claude at the vault and ask: “What did I actually think about X across all my notes?” It answers from 1,200 of your own notes, not the internet your taste, your edge, your dataset. The realistic curve looks like this: Week 1 — 40 notes, graph looks empty, feels like a waste. Month 1 — 300 notes, first real cluster forms. Month 3 — 1,200 notes, and the embeddings start surfacing links you’d long forgotten. Month 6 — you stop googling your own past ideas and just ask the vault. Before — 9 tabs, 3 note apps, 0 memory. After — 1 folder, 1,200 notes, 1 brain that compounds. The gap between people who consume and people who compound isn’t talent, it’s architecture. You build your own life so choose the right path.
0:31

Andrej Karpathy keeps his entire second brain in Obsidian 1 folder of plain text files, nothing else. Here’s the exact setup, free, that turns 1 vault into a brain you can actually query. Why most “second brains” die: Notion is a database you forget to open, ChatGPT memory wipes itself after 30 messages, and both lock your notes inside their cloud. Karpathy rule is the opposite: your notes are the 1 dataset nobody else on earth has, so keep them in plain markdown, own them forever, and let the AI read them later. 3 phases. Phase 1 — Capture with 0 friction. Install Obsidian free, local, 1 hotkey to a daily note. Dump everything into it: ideas, links, quotes, 2-line thoughts, no folders, no tags, no system. Target is 5 notes a day. Phase 2 — Let the graph connect itself. Install Smart Connections and it runs embeddings on every note you’ve ever written, so 2 notes you wrote 4 months apart and never linked by hand suddenly surface as neighbors. That’s the fireworks in the 3D graph each burst is a cluster of ideas your brain forgot it owned. Phase 3 — Query your brain. Point Claude at the vault and ask: “What did I actually think about X across all my notes?” It answers from 1,200 of your own notes, not the internet your taste, your edge, your dataset. The realistic curve looks like this: Week 1 — 40 notes, graph looks empty, feels like a waste. Month 1 — 300 notes, first real cluster forms. Month 3 — 1,200 notes, and the embeddings start surfacing links you’d long forgotten. Month 6 — you stop googling your own past ideas and just ask the vault. Before — 9 tabs, 3 note apps, 0 memory. After — 1 folder, 1,200 notes, 1 brain that compounds. The gap between people who consume and people who compound isn’t talent, it’s architecture. You build your own life so choose the right path.

Spike 1%

16,390 次观看 • 2 个月前

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

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

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

kocer

16,698 次观看 • 2 个月前

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

339,134 次观看 • 3 个月前

CLAUDE + OBSIDIAN + LOOP ENGINEERING = AN AGENT THAT LIVES INSIDE YOUR NOTES Karpathy's second brain runs on something close to this two years of growth he typed almost none of it himself • the loop, four steps on repeat > read - Claude Opus 5 opens the vault instead of a chat window > write - notes and links get edited inside a branch > check - a critic reads the diff and verifies every link > keep - the good change stays, everything else is left alone • the math > cost: 2-4x a single prompt > pays off past a 5% gain > zero notes overwritten, the vault only grows • the whole system, six plain files > CLAUDE.md, skills, subagents, hooks, MCP, plugins > nothing hidden • three ways in > desktop connector - three clicks > Claude Code - full control > Obsidian plugin - you never leave the app the rules that keep it safe: append, never overwrite measure the gain before adding another step don't let it rewrite the whole vault in one turn a loop that never deletes a note is compound interest on your own thinking the stack: 📁 Claude ↳ 📁 Obsidian ↳
0:27

CLAUDE + OBSIDIAN + LOOP ENGINEERING = AN AGENT THAT LIVES INSIDE YOUR NOTES Karpathy's second brain runs on something close to this two years of growth he typed almost none of it himself • the loop, four steps on repeat > read - Claude Opus 5 opens the vault instead of a chat window > write - notes and links get edited inside a branch > check - a critic reads the diff and verifies every link > keep - the good change stays, everything else is left alone • the math > cost: 2-4x a single prompt > pays off past a 5% gain > zero notes overwritten, the vault only grows • the whole system, six plain files > CLAUDE.md, skills, subagents, hooks, MCP, plugins > nothing hidden • three ways in > desktop connector - three clicks > Claude Code - full control > Obsidian plugin - you never leave the app the rules that keep it safe: append, never overwrite measure the gain before adding another step don't let it rewrite the whole vault in one turn a loop that never deletes a note is compound interest on your own thinking the stack: 📁 Claude ↳ 📁 Obsidian ↳

Mr. Buzzoni

27,624 次观看 • 5 天前

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

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

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.
1:25

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.

RetroChainer

13,775 次观看 • 1 个月前

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

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

West Lord

69,192 次观看 • 2 个月前

A developer pointed Claude Code at a 6,200-note Obsidian vault and let it run overnight. The vault was 4 years of markdown. Meeting notes, half-ideas, book highlights. Dead weight. He hadn't opened 90% of it since 2022. He typed one line into the terminal. "Read everything. Find what I forgot." Then he went to bed. By 7 AM, Claude Code had touched all 6,200 files. It wrote 3 new notes. The first mapped 14 ideas scattered across 3 years into one product. He'd never seen they connected. The second listed 22 promises he'd made in old meeting notes and never kept. The third was a full essay. Stitched from 40 fragments. In his own phrasing. He hadn't written a note in 8 months. The vault had been writing itself the whole time. He just couldn't read his own handwriting at scale. Now Claude Code opens the vault every morning at 6:00. It links new notes to old ones. It flags contradictions. It drafts. 2 tools. 1 folder of plain text. No app, no cloud, no subscription. He stopped taking notes to remember them. He takes them now to be read back.
0:29

A developer pointed Claude Code at a 6,200-note Obsidian vault and let it run overnight. The vault was 4 years of markdown. Meeting notes, half-ideas, book highlights. Dead weight. He hadn't opened 90% of it since 2022. He typed one line into the terminal. "Read everything. Find what I forgot." Then he went to bed. By 7 AM, Claude Code had touched all 6,200 files. It wrote 3 new notes. The first mapped 14 ideas scattered across 3 years into one product. He'd never seen they connected. The second listed 22 promises he'd made in old meeting notes and never kept. The third was a full essay. Stitched from 40 fragments. In his own phrasing. He hadn't written a note in 8 months. The vault had been writing itself the whole time. He just couldn't read his own handwriting at scale. Now Claude Code opens the vault every morning at 6:00. It links new notes to old ones. It flags contradictions. It drafts. 2 tools. 1 folder of plain text. No app, no cloud, no subscription. He stopped taking notes to remember them. He takes them now to be read back.

Spike 1%

18,613 次观看 • 2 个月前

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:
22:53

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Akshay 🚀

45,815 次观看 • 2 个月前

iit's wild that this still isn't the default way people use AI. Andrew Ng, a co-founder of Google Brain, gave a talk that crossed 2 million views: stop feeding your AI a folder of notes, build it a graph it can actually think with. his point is simple, stop making your AI read the whole vault to answer one thing. give it a graph, a router that points, an index that scores, edges that link, and it walks straight to the answer. it compounds, cheaper and faster the more you add. here's the whole thing: > point Claude at your notes and have it write a tiny router, your CLAUDE.md > build an index, one line per note, so it always knows where an answer lives > keep each note to one idea, and link the ones that depend on each other > make retrieval run as code, so it scores and opens the right files before the model thinks > tell it to prove the graph beats a flat folder on speed and cost, then keep the index fresh on every write set it up once and your AI stops guessing. it already knows your world before you type a word. full 12-step guide below. bookmark this.
0:23

iit's wild that this still isn't the default way people use AI. Andrew Ng, a co-founder of Google Brain, gave a talk that crossed 2 million views: stop feeding your AI a folder of notes, build it a graph it can actually think with. his point is simple, stop making your AI read the whole vault to answer one thing. give it a graph, a router that points, an index that scores, edges that link, and it walks straight to the answer. it compounds, cheaper and faster the more you add. here's the whole thing: > point Claude at your notes and have it write a tiny router, your CLAUDE.md > build an index, one line per note, so it always knows where an answer lives > keep each note to one idea, and link the ones that depend on each other > make retrieval run as code, so it scores and opens the right files before the model thinks > tell it to prove the graph beats a flat folder on speed and cost, then keep the index fresh on every write set it up once and your AI stops guessing. it already knows your world before you type a word. full 12-step guide below. bookmark this.

KingWilliam

15,099 次观看 • 2 个月前

Local AI 101: open models, Hugging Face, and businesses to build (38 min masterclass) I still think cloud AI is the default for most things, and honestly it should be, the frontier models are the strongest and easiest to use. But something shifted in the last 4-5 months. You can now run genuinely good open models directly on your own laptop, or even your phone. And once you actually try it, it changes how you think about what AI is even for. LOCAL AI, CLEARLY EXPLAINED: 1. The model is the brain doing the thinking. Gemma, Llama, Mistral, and Qwen are the main families, and each is better at different things, some at reasoning, some at coding, some small enough to run on a phone. 2. Hugging Face is the warehouse where you find them. You go there to see what each model is good at, check the license, and grab the compressed versions that run on a normal computer. 3. The software is what runs the model on your machine. Start with LM Studio if you're not technical, it feels like a normal app where you search, download, and start chatting. Ollama is the one you reach for when you want to plug a model into your own apps. 4. The workflow is the actual product you build on top of it all. That's what I'm ideating around for some businesses to create. I think local AI just made a specific kind of business way easier to start. Find an industry that: 1. Sits on sensitive data they'd never paste into ChatGPT 2. Does the same review over and over 3. Runs on software from 2003 Then build a local AI tool that does that review on their own machine, so the data never leaves the building! Take home health agencies. Nurses write visit notes all day, and if a note is missing a detail, the billing gets denied or the audit flags it. Here's how I'd start: 1. Find 5 small agencies. Offer to review a batch of their notes for them. 2. Run the notes through Gemma locally (free, private, no cloud). Read every output yourself. 3. Write down the 20 issues that keep showing up: missing vitals, vague med changes, notes that don't support the billed level. 4. That list of 20 is your checklist. The checklist is the product. 5. Turn it into a local desktop app that flags those 20 things before a note gets submitted. You just went from a service anyone could offer to a product nobody else has, and you learned exactly what to build by doing the work by hand first. Same recipe works for restoration contractors (draft the damage report on-site before the tech leaves) and wealth advisors (catch the compliance landmine in a client email before it sends). Basically the framework is sensitive data, repeated review, ancient software. I think there are tons of businesses like this! Almost none of it clicked for me until I actually started using local AI. So if you take one thing from this, go run a model on your own machine once. Also a fun thing to try with your friends. Feel free to send this to a friend. The episode is live for free on The Startup Ideas Podcast (SIP) 🧃 (thanks to Google for sponsoring today's episode and supporting local AI) I feel like local AI one of those things you need to try for it to really click. Run one model on your own machine and you'll see what I mean! I go way deeper in the full 38 minute masterclass, the models, the setup, and the businesses to build. Link below. LINK TO WATCH: OR WATCH BELOW ON X What do you think of local AI?
38:45

Local AI 101: open models, Hugging Face, and businesses to build (38 min masterclass) I still think cloud AI is the default for most things, and honestly it should be, the frontier models are the strongest and easiest to use. But something shifted in the last 4-5 months. You can now run genuinely good open models directly on your own laptop, or even your phone. And once you actually try it, it changes how you think about what AI is even for. LOCAL AI, CLEARLY EXPLAINED: 1. The model is the brain doing the thinking. Gemma, Llama, Mistral, and Qwen are the main families, and each is better at different things, some at reasoning, some at coding, some small enough to run on a phone. 2. Hugging Face is the warehouse where you find them. You go there to see what each model is good at, check the license, and grab the compressed versions that run on a normal computer. 3. The software is what runs the model on your machine. Start with LM Studio if you're not technical, it feels like a normal app where you search, download, and start chatting. Ollama is the one you reach for when you want to plug a model into your own apps. 4. The workflow is the actual product you build on top of it all. That's what I'm ideating around for some businesses to create. I think local AI just made a specific kind of business way easier to start. Find an industry that: 1. Sits on sensitive data they'd never paste into ChatGPT 2. Does the same review over and over 3. Runs on software from 2003 Then build a local AI tool that does that review on their own machine, so the data never leaves the building! Take home health agencies. Nurses write visit notes all day, and if a note is missing a detail, the billing gets denied or the audit flags it. Here's how I'd start: 1. Find 5 small agencies. Offer to review a batch of their notes for them. 2. Run the notes through Gemma locally (free, private, no cloud). Read every output yourself. 3. Write down the 20 issues that keep showing up: missing vitals, vague med changes, notes that don't support the billed level. 4. That list of 20 is your checklist. The checklist is the product. 5. Turn it into a local desktop app that flags those 20 things before a note gets submitted. You just went from a service anyone could offer to a product nobody else has, and you learned exactly what to build by doing the work by hand first. Same recipe works for restoration contractors (draft the damage report on-site before the tech leaves) and wealth advisors (catch the compliance landmine in a client email before it sends). Basically the framework is sensitive data, repeated review, ancient software. I think there are tons of businesses like this! Almost none of it clicked for me until I actually started using local AI. So if you take one thing from this, go run a model on your own machine once. Also a fun thing to try with your friends. Feel free to send this to a friend. The episode is live for free on The Startup Ideas Podcast (SIP) 🧃 (thanks to Google for sponsoring today's episode and supporting local AI) I feel like local AI one of those things you need to try for it to really click. Run one model on your own machine and you'll see what I mean! I go way deeper in the full 38 minute masterclass, the models, the setup, and the businesses to build. Link below. LINK TO WATCH: OR WATCH BELOW ON X What do you think of local AI?

GREG ISENBERG

32,410 次观看 • 17 天前

Most people start Obsidian the wrong way. They import 10,000 notes. Build 50 folders. Install 20 plugins. Then quit a week later. If I had to restart Obsidian today, I’d do the opposite: • Start with 5 meaningful notes • Create ZERO folders • Ignore plugins completely • Focus only on connecting ideas That’s the real unlock. Obsidian isn’t a notes app. It’s a personal internet for your mind. The magic happens when you use one simple prompt: “This reminds me of…” A quote links to a book. A book links to a song. A song links to a memory. A memory links to an insight. That’s how real thinking compounds. The goal isn’t collecting information. It’s building connections your brain can return to later. AI can summarize notes. But only YOU can create meaningful links between ideas. That’s where the leverage is. Follow Dami-Defi for more AI alpha.
12:10

Most people start Obsidian the wrong way. They import 10,000 notes. Build 50 folders. Install 20 plugins. Then quit a week later. If I had to restart Obsidian today, I’d do the opposite: • Start with 5 meaningful notes • Create ZERO folders • Ignore plugins completely • Focus only on connecting ideas That’s the real unlock. Obsidian isn’t a notes app. It’s a personal internet for your mind. The magic happens when you use one simple prompt: “This reminds me of…” A quote links to a book. A book links to a song. A song links to a memory. A memory links to an insight. That’s how real thinking compounds. The goal isn’t collecting information. It’s building connections your brain can return to later. AI can summarize notes. But only YOU can create meaningful links between ideas. That’s where the leverage is. Follow Dami-Defi for more AI alpha.

Dami-Defi

71,024 次观看 • 4 个月前

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

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

Shadow Nick

47,058 次观看 • 2 个月前