Loading video...

Video Failed to Load

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

exploring shapes of thoughts: extracted my obsidian notes' embeddings and arranges them as a 3d network using 3 different topologies: - centralized: one core idea connecting all - decentralized: notes cluster into themed hubs - distributed: edges labeled by llm describing how ideas connect

Kat ⊷ the Poet Engineer

86,533 subscribers

615,070 views • 6 months ago •via X (Twitter)

Arts Education Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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.

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

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

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

Spike 1%

12,346 views • 1 month ago

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

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

GREG ISENBERG

1,136,369 views • 5 months ago

THIS GUY TURNED OBSIDIAN INTO A DIGITAL TWIN OF HIS OWN BRAIN, 400 PLUS NODES, 6 KNOWLEDGE CLUSTERS, 1 LOCAL VAULT, AND A MAP THAT GETS SMARTER WITH EVERY NOTE 00:05 the graph begins as one dense sphere, then individual paths light up across the screen, showing how a single note can connect to dozens of ideas instead of disappearing inside another folder. most people store information in straight lines, one file after another. his vault grows like a network, research connects to projects, projects connect to decisions, and old notes keep feeding new work months later. after 100 notes, it still feels like storage. around 300, clusters begin exposing repeated interests, unfinished threads, and topics that keep returning even after he stops thinking about them. with claude connected, the network becomes usable context. instead of pasting 20 files into one chat, an agent can follow 5 linked notes, pull original sources, compare old decisions, and write the result back into the same vault. a real second brain is not the pretty graph. it is a local system where every new thought strengthens old connections, buried ideas come back when needed, and knowledge keeps compounding without leaving your machine.

THIS GUY TURNED OBSIDIAN INTO A DIGITAL TWIN OF HIS OWN BRAIN, 400 PLUS NODES, 6 KNOWLEDGE CLUSTERS, 1 LOCAL VAULT, AND A MAP THAT GETS SMARTER WITH EVERY NOTE 00:05 the graph begins as one dense sphere, then individual paths light up across the screen, showing how a single note can connect to dozens of ideas instead of disappearing inside another folder. most people store information in straight lines, one file after another. his vault grows like a network, research connects to projects, projects connect to decisions, and old notes keep feeding new work months later. after 100 notes, it still feels like storage. around 300, clusters begin exposing repeated interests, unfinished threads, and topics that keep returning even after he stops thinking about them. with claude connected, the network becomes usable context. instead of pasting 20 files into one chat, an agent can follow 5 linked notes, pull original sources, compare old decisions, and write the result back into the same vault. a real second brain is not the pretty graph. it is a local system where every new thought strengthens old connections, buried ideas come back when needed, and knowledge keeps compounding without leaving your machine.

Gipp 🦅

20,183 views • 1 month ago

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.

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

This guy opened Obsidian 90 days ago with 200 isolated notes rotting in folders he had not opened in 6 months. He just started linking. One note at a time. One connection at a time. Every single day. Today he has 847 notes and over 2,300 connections between them. The graph does not look like folders. It looks like a brain. And it shows him what he actually thinks about, not what he assumed he cared about. This is exactly why I built my Web Clipper workflow around connection and not storage. If you want to see how I turn heavy books and dense data into actual insights inside Obsidian, I wrote about my 6 best Web Clipper templates that I use daily. Link in the post. He is not smarter than he was 90 days ago. He just stopped filing and started linking. His notes are not stored. They are alive. If you have been using Obsidian as a glorified Google Drive folder, like and bookmark this. 90 days is all it takes.

This guy opened Obsidian 90 days ago with 200 isolated notes rotting in folders he had not opened in 6 months. He just started linking. One note at a time. One connection at a time. Every single day. Today he has 847 notes and over 2,300 connections between them. The graph does not look like folders. It looks like a brain. And it shows him what he actually thinks about, not what he assumed he cared about. This is exactly why I built my Web Clipper workflow around connection and not storage. If you want to see how I turn heavy books and dense data into actual insights inside Obsidian, I wrote about my 6 best Web Clipper templates that I use daily. Link in the post. He is not smarter than he was 90 days ago. He just stopped filing and started linking. His notes are not stored. They are alive. If you have been using Obsidian as a glorified Google Drive folder, like and bookmark this. 90 days is all it takes.

Kanika

33,755 views • 2 months ago

How did Atiq run the fake currency network? Dr. Vikram Singh, Former DGP of UP. Former UP DGP Dr Vikram Singh revealed in a podcast that Atiq Ahmed ran the fake currency network in the following manner: 🔴 The ISI had set up a factory in Bahawalpur, Pakistan, where the die machines of the Nashik Security Press, auctioned by Abdul Karim Telgi, were sent as scrap. 🔴 ISI, with the help of its sister agencies, procured raw material for counterfeit currency from Germany. 🔴 The fake notes reached Nepal via Nepal Pakistan International Airlines and then entered India via the UP-Nepal border (771 km, 7 districts: Pilibhit, Lakhimpur Kheri, Bahraich, Balrampur, Shravasti, Maharajganj). 🔴 Himalayan Bank was formed as a joint venture between Pakistan's Habib Bank and Nepal's National Bank. Its branches were opened on the UP-Nepal border to exchange fake and real currency notes. 🔴 Atiq did not print the notes himself, but he was a facilitator/sleeper cell of Ustrad – he provided manpower, logistics supply and protected umbrella. 🔴 Fake notes were mixed with real notes and real notes were mixed with fake notes (Exchange of 4 real notes and 4 fake notes in one branch) The former DGP said that Pakistan had injected fake currency worth around Rs 7-8 lakh crore into the Indian economy, and after demonetisation, people involved in this business in Pakistan committed suicide as all their assets became worthless. Credit : TRP/RJ Raunac

How did Atiq run the fake currency network? Dr. Vikram Singh, Former DGP of UP. Former UP DGP Dr Vikram Singh revealed in a podcast that Atiq Ahmed ran the fake currency network in the following manner: 🔴 The ISI had set up a factory in Bahawalpur, Pakistan, where the die machines of the Nashik Security Press, auctioned by Abdul Karim Telgi, were sent as scrap. 🔴 ISI, with the help of its sister agencies, procured raw material for counterfeit currency from Germany. 🔴 The fake notes reached Nepal via Nepal Pakistan International Airlines and then entered India via the UP-Nepal border (771 km, 7 districts: Pilibhit, Lakhimpur Kheri, Bahraich, Balrampur, Shravasti, Maharajganj). 🔴 Himalayan Bank was formed as a joint venture between Pakistan's Habib Bank and Nepal's National Bank. Its branches were opened on the UP-Nepal border to exchange fake and real currency notes. 🔴 Atiq did not print the notes himself, but he was a facilitator/sleeper cell of Ustrad – he provided manpower, logistics supply and protected umbrella. 🔴 Fake notes were mixed with real notes and real notes were mixed with fake notes (Exchange of 4 real notes and 4 fake notes in one branch) The former DGP said that Pakistan had injected fake currency worth around Rs 7-8 lakh crore into the Indian economy, and after demonetisation, people involved in this business in Pakistan committed suicide as all their assets became worthless. Credit : TRP/RJ Raunac

Augadh

131,959 views • 4 months ago

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.

West Lord

75,208 views • 1 month ago

A Stanford 26-year-old spent 2 years turning 11,400 Obsidian notes into a neural net that finishes his sentences. It started as a folder called “misc” with 43 PDF in it. Most vaults die around 300 notes, because nothing connects and nothing comes back roughly 90% of what you save gets read once, on the day you save it. He fixed it by treating retrieval as the product and storage as the leftovers. Phase 1: Atomize (months 1-3) One idea per note, 200 words max, title written as a claim instead of a topic. “Attention is a filter, not a spotlight” beats “Notes on attention.” He rewrote 1,200 old notes this way and the vault shrank from 2,800 files to 1,600 usable ones. Phase 2: Embed locally (months 4-8) Ollama running nomic-embed-text on a Mac Mini M4, every note chunked at 512 tokens with 64-token overlap, all of it dumped into a local ChromaDB. 11,400 notes became 38,000 vectors and 1.2 GB on disk. Query time 0.4 seconds, cost $0 a month, nothing leaving the machine. Phase 3: Kill the hallucinations (months 9-14) Plain cosine search returned garbage about 30% of the time, so he bolted on a re-ranker and one hard rule: every retrieved chunk carries its source note title into the answer, and no citation means no answer. Wrong recalls fell from 1 in 4 to 1 in 30. Phase 4: Make it speak first (months 15-24) A nightly job reads the day’s writing, pulls the 5 oldest notes with the highest similarity, and drops 3 questions into tomorrow’s daily note. He stopped searching the vault somewhere in month 17 now it opens the conversation before he does. Before: 2,800 notes, 0 reused, 6 weeks per paper draft. After: 11,400 notes, 60-70 surfaced every week unasked, 9 days per draft. The whole stack is 4 pieces Obsidian, Ollama, ChromaDB, and a 40-line Python script that runs at 2 AM. Total software spend across 24 months: $0. Most people build a second brain to store things they will never open again. He stopped writing to remember. He writes so the machine can remind him.

A Stanford 26-year-old spent 2 years turning 11,400 Obsidian notes into a neural net that finishes his sentences. It started as a folder called “misc” with 43 PDF in it. Most vaults die around 300 notes, because nothing connects and nothing comes back roughly 90% of what you save gets read once, on the day you save it. He fixed it by treating retrieval as the product and storage as the leftovers. Phase 1: Atomize (months 1-3) One idea per note, 200 words max, title written as a claim instead of a topic. “Attention is a filter, not a spotlight” beats “Notes on attention.” He rewrote 1,200 old notes this way and the vault shrank from 2,800 files to 1,600 usable ones. Phase 2: Embed locally (months 4-8) Ollama running nomic-embed-text on a Mac Mini M4, every note chunked at 512 tokens with 64-token overlap, all of it dumped into a local ChromaDB. 11,400 notes became 38,000 vectors and 1.2 GB on disk. Query time 0.4 seconds, cost $0 a month, nothing leaving the machine. Phase 3: Kill the hallucinations (months 9-14) Plain cosine search returned garbage about 30% of the time, so he bolted on a re-ranker and one hard rule: every retrieved chunk carries its source note title into the answer, and no citation means no answer. Wrong recalls fell from 1 in 4 to 1 in 30. Phase 4: Make it speak first (months 15-24) A nightly job reads the day’s writing, pulls the 5 oldest notes with the highest similarity, and drops 3 questions into tomorrow’s daily note. He stopped searching the vault somewhere in month 17 now it opens the conversation before he does. Before: 2,800 notes, 0 reused, 6 weeks per paper draft. After: 11,400 notes, 60-70 surfaced every week unasked, 9 days per draft. The whole stack is 4 pieces Obsidian, Ollama, ChromaDB, and a 40-line Python script that runs at 2 AM. Total software spend across 24 months: $0. Most people build a second brain to store things they will never open again. He stopped writing to remember. He writes so the machine can remind him.

West Lord

170,060 views • 20 days ago

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

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

Yarchi

58,186 views • 2 months ago

New course: A2A: The Agent2Agent Protocol, built with Google Cloud Tech and IBM Research, and taught by Holt Skinner, Ivan Nardini, and Sandi Besen. Connecting agents built with different frameworks usually requires extensive custom integration. This short course teaches you A2A, the open protocol standardizing how agents discover each other and communicate. Since IBM’s ACP (Agent Communication Protocol) joined forces with A2A, A2A has emerged as the industry standard. In this course, you'll build a healthcare multi-agent system where agents built with different frameworks, such as Google ADK (Agent Development Kit) and LangGraph, collaborate through A2A. You'll wrap each agent as an A2A server, build A2A clients to connect to them, and orchestrate them into sequential and hierarchical workflows. Skills you'll gain: - Expose agents from different frameworks as A2A servers to make them discoverable and interoperable - Chain A2A agents sequentially using ADK, where one agent's output feeds into the next - Connect A2A agents to external data sources using MCP (Model Context Protocol) - Deploy A2A agents using Agent Stack, IBM's open-source infrastructure Join and learn the protocol standardizing agent collaboration!

New course: A2A: The Agent2Agent Protocol, built with Google Cloud Tech and IBM Research, and taught by Holt Skinner, Ivan Nardini, and Sandi Besen. Connecting agents built with different frameworks usually requires extensive custom integration. This short course teaches you A2A, the open protocol standardizing how agents discover each other and communicate. Since IBM’s ACP (Agent Communication Protocol) joined forces with A2A, A2A has emerged as the industry standard. In this course, you'll build a healthcare multi-agent system where agents built with different frameworks, such as Google ADK (Agent Development Kit) and LangGraph, collaborate through A2A. You'll wrap each agent as an A2A server, build A2A clients to connect to them, and orchestrate them into sequential and hierarchical workflows. Skills you'll gain: - Expose agents from different frameworks as A2A servers to make them discoverable and interoperable - Chain A2A agents sequentially using ADK, where one agent's output feeds into the next - Connect A2A agents to external data sources using MCP (Model Context Protocol) - Deploy A2A agents using Agent Stack, IBM's open-source infrastructure Join and learn the protocol standardizing agent collaboration!

Andrew Ng

86,175 views • 6 months ago

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

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

West Lord

68,938 views • 1 month ago

From Zero to One: The NodeOps Story In just two years, NodeOps has grown from a 3-person team into: → A protocol generating $4.4M+ in revenue → One of the leading DePIN projects → A community of 700K+ verified users → A network powering 23K+ deployments, 5K+ machines, and 1K+ providers Our mission is simple: make infrastructure invisible and empower builders to focus on what matters, their ideas. That’s why we built Autogen, a one-stop platform for deployment, scaling, and coordination. Autogen makes it seamless to go from idea to production with AI-powered deployment and zero downtime. NodeOps isn’t just infrastructure, it’s the foundation for the next wave of AI, data, and decentralized applications. At the core of it all is $NODE, with a dynamic burn/mint model directly tied to real network revenue. Watch Sheena ✈️ Singapore break it all down 👇🏻

From Zero to One: The NodeOps Story In just two years, NodeOps has grown from a 3-person team into: → A protocol generating $4.4M+ in revenue → One of the leading DePIN projects → A community of 700K+ verified users → A network powering 23K+ deployments, 5K+ machines, and 1K+ providers Our mission is simple: make infrastructure invisible and empower builders to focus on what matters, their ideas. That’s why we built Autogen, a one-stop platform for deployment, scaling, and coordination. Autogen makes it seamless to go from idea to production with AI-powered deployment and zero downtime. NodeOps isn’t just infrastructure, it’s the foundation for the next wave of AI, data, and decentralized applications. At the core of it all is $NODE, with a dynamic burn/mint model directly tied to real network revenue. Watch Sheena ✈️ Singapore break it all down 👇🏻

NodeOps

22,816 views • 10 months ago

Anthropic engineer just built a second brain that reads 3 files instead of 5,000, and cut the token bill 40% no orchestrator, no plugin, just a router file, an index, and code that scores before the model ever opens anything point claude at a flat folder of notes and every question reads all of them, that’s the default and it’s expensive this breakdown turns that exact pattern into a system anyone can run CLAUDE.md → index.md → nodes → edges → retrieval as code → memory → ship it twelve steps, one shared rule, evidence lives in the index, the model reads three files while the notes folder still holds thousands the stale index test, one line drifts and the whole graph quietly turns back into the pile it was built to escape, no exceptions save it and watch, then read the article below

Anthropic engineer just built a second brain that reads 3 files instead of 5,000, and cut the token bill 40% no orchestrator, no plugin, just a router file, an index, and code that scores before the model ever opens anything point claude at a flat folder of notes and every question reads all of them, that’s the default and it’s expensive this breakdown turns that exact pattern into a system anyone can run CLAUDE.md → index.md → nodes → edges → retrieval as code → memory → ship it twelve steps, one shared rule, evidence lives in the index, the model reads three files while the notes folder still holds thousands the stale index test, one line drifts and the whole graph quietly turns back into the pile it was built to escape, no exceptions save it and watch, then read the article below

leopardracer

37,304 views • 22 days ago

THE CREATOR OF OBSIDIAN JUST SHIPPED HIS OWN CLAUDE SKILLS PACK 44,000 developers already installed it. most people building second brains with claude have no idea it exists these aren't community skills. they're written by kepano himself - the person who built obsidian. that means they respect obsidian's actual conventions: markdown, bases, JSON canvas, backlinks, plugins, all of it drop them into your claude skills folder once. next time you say "summarize my notes about karpathy" or "extract this article to my inbox," the right skill wakes up automatically. no prompt engineering. no manual context. no config i tested 10 claude + obsidian repos to write my full breakdown. this is the one with the highest trust factor - because the person shipping it is the one who defined what an obsidian vault even looks like the full ranked breakdown of all 10 is in the article i test things like this on myself and share the results. follow kai if you want to see what's next

THE CREATOR OF OBSIDIAN JUST SHIPPED HIS OWN CLAUDE SKILLS PACK 44,000 developers already installed it. most people building second brains with claude have no idea it exists these aren't community skills. they're written by kepano himself - the person who built obsidian. that means they respect obsidian's actual conventions: markdown, bases, JSON canvas, backlinks, plugins, all of it drop them into your claude skills folder once. next time you say "summarize my notes about karpathy" or "extract this article to my inbox," the right skill wakes up automatically. no prompt engineering. no manual context. no config i tested 10 claude + obsidian repos to write my full breakdown. this is the one with the highest trust factor - because the person shipping it is the one who defined what an obsidian vault even looks like the full ranked breakdown of all 10 is in the article i test things like this on myself and share the results. follow kai if you want to see what's next

kai

253,935 views • 11 days ago

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

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

Spike 1%

58,428 views • 1 month ago

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

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

Yarchi

141,580 views • 2 months ago

here's how I generate beautiful emails using Paper and claude code for humblytics 1) I scraped all of our existing emails and outlined in our obsidian notes 2) ran my marketing-strategist skill to analzye existing open/close rates, pull context from our app and rewrite the entire email 3) connect to the paper mcp, open up claude code, and reference the new emails it just rewrote 4) design the entire email in paper, refine it, then when you're done ask claude code to export is as a .mjml file 5) load the .mjml file and you're done you now have emails that are on brand and designed to your specs

amirmxt

11,222 views • 3 months ago

I used to be chained to my desk, switching between apps and losing my train of thought. WhatsApp for quick chats, LinkedIn for professional posts, X for quick thoughts... it was a productivity nightmare. You know that feeling of having a great idea for a post, but by the time you open the right app, the inspiration is gone? That was my reality. As a creator, I'm always on the move, and my work happens everywhere. I needed a tool that could keep up with my brain, no matter which app I'm using. Then I started using Typeless to dictate my thoughts directly into any app. This video shows how I can now draft a LinkedIn post, reply to a WhatsApp message, and create a tweet, all without touching my keyboard. It’s been a game-changer for my workflow. What used to be a fragmented process is now a seamless flow of ideas. Try it here:

I used to be chained to my desk, switching between apps and losing my train of thought. WhatsApp for quick chats, LinkedIn for professional posts, X for quick thoughts... it was a productivity nightmare. You know that feeling of having a great idea for a post, but by the time you open the right app, the inspiration is gone? That was my reality. As a creator, I'm always on the move, and my work happens everywhere. I needed a tool that could keep up with my brain, no matter which app I'm using. Then I started using Typeless to dictate my thoughts directly into any app. This video shows how I can now draft a LinkedIn post, reply to a WhatsApp message, and create a tweet, all without touching my keyboard. It’s been a game-changer for my workflow. What used to be a fragmented process is now a seamless flow of ideas. Try it here:

FELIX

121,641 views • 9 months ago

This is, by far, one of the best uses of modern AI. If you don't use embeddings when querying your database, you are definitely leaving a lot on the table. In this video, I'll show you how to run semantic searches using OpenAI and PostgreSQL. It's all thanks to Pgai, an open-source PostgreSQL extension: Here's what will happen: 1. We'll create a simple table with news articles 2. We'll generate embeddings for those articles 3. We'll run queries on top of those embeddings For this video, I generated the embeddings using a simple query, but pgai Vectorizer would do the same automatically as new information makes it into the database. This is awesome! If you have a PostgreSQL database with data you are searching over, you should start experimenting with semantic searches immediately. For most use cases, a combination of full-text search + semantic search is the best approach. If you don't have a PostgreSQL database around, you can try free for 30 days using Timescale: Thanks to the TimescaleDB (by Tiger Data) team for partnering with me on this post!

This is, by far, one of the best uses of modern AI. If you don't use embeddings when querying your database, you are definitely leaving a lot on the table. In this video, I'll show you how to run semantic searches using OpenAI and PostgreSQL. It's all thanks to Pgai, an open-source PostgreSQL extension: Here's what will happen: 1. We'll create a simple table with news articles 2. We'll generate embeddings for those articles 3. We'll run queries on top of those embeddings For this video, I generated the embeddings using a simple query, but pgai Vectorizer would do the same automatically as new information makes it into the database. This is awesome! If you have a PostgreSQL database with data you are searching over, you should start experimenting with semantic searches immediately. For most use cases, a combination of full-text search + semantic search is the best approach. If you don't have a PostgreSQL database around, you can try free for 30 days using Timescale: Thanks to the TimescaleDB (by Tiger Data) team for partnering with me on this post!

Santiago

110,133 views • 1 year ago