Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

59,408 Aufrufe • vor 3 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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

Yarchi

58,186 Aufrufe • vor 1 Monat

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,542 Aufrufe • vor 21 Tagen

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

Yarchi

55,345 Aufrufe • vor 1 Monat

OBSIDIAN'S CEO AND ANDREJ KARPATHY JUST QUIETLY KILLED THE SECOND BRAIN INDUSTRY. IT STARTED AS A SINGLE GIST. 21 MILLION PEOPLE READ IT BEFORE ANYONE NOTICED WHAT IT ACTUALLY MEANT 42,000 stars. 5 skill files. 0 databases the idea: stop treating your notes like a diary. treat them like a codebase. Obsidian is the editor. Claude Code is the engineer. your notes are the thing being built three commands run the whole thing. one drops in anything - a video, a PDF, a random thought - and splits it into small linked pieces that plug straight into what you already wrote one lets you ask a question and get an answer pulled from your own words, your own pages, not a guess from a model that's never met you. one runs quietly every week, hunts down the notes that contradict each other, deletes what's gone stale, and reconnects the orphaned pages nobody linked back then the Obsidian CEO shipped something that wasn't an "AI button" - five small skill files that teach Claude to speak Obsidian's own language natively. no broken links. no messy imports 42,000 stars. weeks old Karpathy pointed the whole thing at 100 of his own articles. 400,000 words. longer than most PhD dissertations. he didn't write it. it links itself. it audits itself. it never sleeps no vector db. no subscription. no chunking config. no reranker. just folders of text and an agent that does the one job humans always quit halfway through - keeping the filing system honest most vaults are graveyards. this one reads itself before you wake up

chewa.

18,304 Aufrufe • vor 5 Tagen

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,132,600 Aufrufe • vor 4 Monaten

One of the smartest things you can do with Fable 5 right now: Re-create your AI second brain to log all your business ideas, personal context, and important data. The first time I built an AI second brain was with Opus, but I recently re-created it with Fable 5, and it blew my mind. Here's exactly how to get started: Step 1. Set up your Obsidian vault Download Obsidian from Obsidian dot md if you haven't already. Then, go ahead and create a clean vault with your most important folders. For example: /ideas → business ideas, content angles, random thoughts /context → who you are, your business, your goals, your stack /data → important numbers, portfolios, metrics /log → daily entries, decisions, lessons learned This is your database. Everything Fable reads lives here. Step 2. Connect Fable 5 to your vault I like this Claude Code prompt: "/goal connect to my Obsidian vault at [path] and act as my second brain orchestrator. Read everything in /context before every session. Log anything new I tell you to /log with today's date." Fable now reads your vault before it answers anything - it knows your business, your goals, your history. Step 3. Build the self-update habit Every time you have an idea, a decision, or a lesson, tell Fable: "Log this to my second brain: [thought]" Step 4. Start querying it You can start sending prompts like: → "What are the most common themes across my last 30 ideas?" → "Based on my context, what should I be prioritising this week?" → "What decisions have I made about my content strategy so far?" Opus was good at this, but Fable is on another level. I feel the depth of reasoning it brings to your data is genuinely unlike anything I've used before. Some might argue it's a bit of overkill to use Fable for a simple second-brain setup, but if you have the means, it's 100% worth it. Build this once, and it'll compound forever.

Miles Deutscher

88,771 Aufrufe • vor 6 Tagen