Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

THIS GUY HIT HIS DAILY CLAUDE LIMIT BUILDING A KNOWLEDGE GRAPH. THE SYSTEM KEPT RUNNING WITHOUT HIM he opened obsidian at 6am and claude had already read everything new connections, a brief, one question worth thinking about today his coworkers are still copy-pasting context into every session he stopped... show more

leopardracer

10,026 subscribers

87,564 Aufrufe • vor 5 Monaten •via X (Twitter)

Bildung Nachrichten & Politik Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

THIS GUY OPENED OBSIDIAN AND SAW HIS ENTIRE KNOWLEDGE AS A NETWORK AND HE BUILT IT IN 90 DAYS one note at a time and one link at a time now the graph shows him what he actually thinks about and not what he assumed he cared about six months ago he had 200 isolated notes sitting in folders nobody visits today every idea he has connects to something he wrote in the past a thought from january becomes context for a decision in may without him remembering january even happened his coworkers are still searching for files by name and finding nothing useful the only difference is he stopped filing and started linking his notes are not stored they are connected like & bookmark this if you’ve been using obsidian as a filing cabinet this whole time

THIS GUY OPENED OBSIDIAN AND SAW HIS ENTIRE KNOWLEDGE AS A NETWORK AND HE BUILT IT IN 90 DAYS one note at a time and one link at a time now the graph shows him what he actually thinks about and not what he assumed he cared about six months ago he had 200 isolated notes sitting in folders nobody visits today every idea he has connects to something he wrote in the past a thought from january becomes context for a decision in may without him remembering january even happened his coworkers are still searching for files by name and finding nothing useful the only difference is he stopped filing and started linking his notes are not stored they are connected like & bookmark this if you’ve been using obsidian as a filing cabinet this whole time

leopardracer

144,922 Aufrufe • vor 5 Monaten

The reason Claude keeps disappointing you is not Claude - it’s you. Every session - explain yourself from scratch. Every session - it forgets you exist. Every session - same mistakes. Same corrections. Same waste. That’s not AI. That’s a goldfish with a keyboard. One file broke that loop permanently. 21 lines. That’s it. Now Claude knows his voice. His rules. His decisions. What failed. What worked. Where he left off. He doesn’t explain himself. He doesn’t repeat himself. He just builds. While you’re re-explaining your job for the 200th time - he already shipped. Tony Stark didn’t prompt J.A.R.V.I.S. He talked to it like it knew him. Because it did. This guy has that. In a wine bar. On a laptop. With a text file. 82,000 GitHub stars. #1 trending. And you still don’t have it set up. Bookmark this before you forget. Because you will forget. And tomorrow you’ll be explaining yourself to Claude again.

The reason Claude keeps disappointing you is not Claude - it’s you. Every session - explain yourself from scratch. Every session - it forgets you exist. Every session - same mistakes. Same corrections. Same waste. That’s not AI. That’s a goldfish with a keyboard. One file broke that loop permanently. 21 lines. That’s it. Now Claude knows his voice. His rules. His decisions. What failed. What worked. Where he left off. He doesn’t explain himself. He doesn’t repeat himself. He just builds. While you’re re-explaining your job for the 200th time - he already shipped. Tony Stark didn’t prompt J.A.R.V.I.S. He talked to it like it knew him. Because it did. This guy has that. In a wine bar. On a laptop. With a text file. 82,000 GitHub stars. #1 trending. And you still don’t have it set up. Bookmark this before you forget. Because you will forget. And tomorrow you’ll be explaining yourself to Claude again.

leopardracer

10,804 Aufrufe • vor 6 Monaten

A 22-YEAR-OLD FROM BEIJING BUILT A SECOND BRAIN WITH CLAUDE, MAKES $14,000/MONTH AND HIS AI REMEMBERS EVERY DECISION HE'S EVER MADE Most people open ChatGPT, ask a question and start from zero next session, re-explaining the same context every single time and losing 15–40 minutes per session doing it. He built infrastructure where Claude reads, writes and connects everything in Obsidian automatically so it never resets and compounds with every conversation. This morning he needed a client strategy from 3 months ago. Claude pulled it up instantly and drafted a full email reply in under 20 minutes using context it had been building for months across 6,000+ sessions. Every session adds to the last one and the system now saves him 2–3 hours every single day - 30–90 minutes from automated morning briefing alone, before he even opens his laptop. repo: The repo is free. The advantage it creates is not.

A 22-YEAR-OLD FROM BEIJING BUILT A SECOND BRAIN WITH CLAUDE, MAKES $14,000/MONTH AND HIS AI REMEMBERS EVERY DECISION HE'S EVER MADE Most people open ChatGPT, ask a question and start from zero next session, re-explaining the same context every single time and losing 15–40 minutes per session doing it. He built infrastructure where Claude reads, writes and connects everything in Obsidian automatically so it never resets and compounds with every conversation. This morning he needed a client strategy from 3 months ago. Claude pulled it up instantly and drafted a full email reply in under 20 minutes using context it had been building for months across 6,000+ sessions. Every session adds to the last one and the system now saves him 2–3 hours every single day - 30–90 minutes from automated morning briefing alone, before he even opens his laptop. repo: The repo is free. The advantage it creates is not.

Noisy

23,679 Aufrufe • vor 5 Monaten

THIS GUY BUILT A SYSTEM THAT GETS SMARTER EVERY TIME HE USES IT AND IT LOOKS LIKE A GALAXY he types one command into Claude Code it finds sources, runs analysis through NotebookLM, saves everything to Obsidian automatically graph in the background is every idea he's ever researched - all linked together system handles the research so he only has to think about what to do with it most people are still copy-pasting into Notion and losing everything by next week full setup in the article

THIS GUY BUILT A SYSTEM THAT GETS SMARTER EVERY TIME HE USES IT AND IT LOOKS LIKE A GALAXY he types one command into Claude Code it finds sources, runs analysis through NotebookLM, saves everything to Obsidian automatically graph in the background is every idea he's ever researched - all linked together system handles the research so he only has to think about what to do with it most people are still copy-pasting into Notion and losing everything by next week full setup in the article

monokern

45,188 Aufrufe • vor 5 Monaten

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

10,799 Aufrufe • vor 4 Monaten

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,381 Aufrufe • vor 4 Monaten

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

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

0xMarioNawfal

68,251 Aufrufe • vor 6 Monaten

Boris Cherny, the creator of Claude Code at Anthropic, just explained how he runs thousands of agents from his phone while he sleeps in this talk he breaks down exactly how he manages thousands of agents from his phone: - the 14% you lose to CLAUDE.md before typing a word - the architecture behind running a few thousand agents overnight - why the system matters more than the tool - the knowledge structure that makes everything findable, connected, and useful if you've been using Claude for months and every conversation still starts from scratch with zero memory and zero context, you don't have a system. you have a chat history instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed the guide is in the article below

Boris Cherny, the creator of Claude Code at Anthropic, just explained how he runs thousands of agents from his phone while he sleeps in this talk he breaks down exactly how he manages thousands of agents from his phone: - the 14% you lose to CLAUDE.md before typing a word - the architecture behind running a few thousand agents overnight - why the system matters more than the tool - the knowledge structure that makes everything findable, connected, and useful if you've been using Claude for months and every conversation still starts from scratch with zero memory and zero context, you don't have a system. you have a chat history instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed the guide is in the article below

Khairallah AL-Awady

86,507 Aufrufe • vor 5 Monaten

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 Aufrufe • vor 5 Monaten

ONE OF ANTHROPIC'S CODERS SHARED HIS "SECOND BRAIN" HE'S BEEN BUILDING FOR 3 MONTHS. I WASN'T READY FOR WHAT I SAW he didn't post this on twitter. didn't make a thread. didn't record a youtube video. just showed me on a call and said "look what i've got" when i opened it - 2000+ notes. all connected to each other. looked like a map of the universe and at the center of it all - one file. CLAUDE.md it's not a prompt. it's a full profile of a person. who he is. how he thinks. what he's working on. where he gets stuck. how he wants the AI to talk to him. even his weaknesses claude reads this file first. every time. automatically. never starts a conversation from zero i asked him "so what did this change?" he said: "i stopped spending time explaining. now i spend time thinking" but that's just the beginning. every project has its own folder. clean structure. when he works on something - claude only sees that project. not the entire chaos anything he does more than once is saved as a skill. one line and claude does it his way and at 7am every day claude walks through the entire vault on its own. finds new stuff. links it. cleans what's stale. writes him 3 lines: what changed overnight he wakes up and the brain already worked and here's what got me the most: it's all just text files. no cloud. no subscription. no dependency on one service. if a better model drops tomorrow he just points it at the same folder he basically uploaded himself into a file system. and now AI doesn't guess who he is. AI knows most people use claude like google with manners. this guy built himself an external memory that grows every day full breakdown in the video tomorrow i'll show how i set this up myself in one evening. if you don't follow - you won't see it

kai

47,527 Aufrufe • vor 3 Monaten

A 14-year-old from China built three separate AI brains connected to Claude Code - and each one grows every day on its own. One brain for code, one for projects, one for everything else in his life. 600+ conversations on one topic in a single node - everything linked, everything accessible in one request without copying between tabs. But the main thing isn't storage. If Claude Code made a mistake and he corrected it once - the system remembered. That same mistake never happened again. No re-explaining context, no starting from zero - Claude already knows how he thinks. Instead of one giant messy file- a stack of smaller brains passing context to each other. Brain to brain to brain - just stacking intelligence while his classmates do homework by hand.

A 14-year-old from China built three separate AI brains connected to Claude Code - and each one grows every day on its own. One brain for code, one for projects, one for everything else in his life. 600+ conversations on one topic in a single node - everything linked, everything accessible in one request without copying between tabs. But the main thing isn't storage. If Claude Code made a mistake and he corrected it once - the system remembered. That same mistake never happened again. No re-explaining context, no starting from zero - Claude already knows how he thinks. Instead of one giant messy file- a stack of smaller brains passing context to each other. Brain to brain to brain - just stacking intelligence while his classmates do homework by hand.

Noisy

22,720 Aufrufe • vor 6 Monaten

"YOU'RE NOT SUPPOSED TO PROMPT CLAUDE. YOU'RE SUPPOSED TO BUILD A SYSTEM THAT PROMPTS ITSELF." Boris Cherny, who built Claude Code, said it plainly. In 26 minutes he shows exactly how to build one from scratch, step by step. Most people are still doing every part of this by hand. Watch the session, then save the guide below. Bookmark this. Follow CyrilXBT

"YOU'RE NOT SUPPOSED TO PROMPT CLAUDE. YOU'RE SUPPOSED TO BUILD A SYSTEM THAT PROMPTS ITSELF." Boris Cherny, who built Claude Code, said it plainly. In 26 minutes he shows exactly how to build one from scratch, step by step. Most people are still doing every part of this by hand. Watch the session, then save the guide below. Bookmark this. Follow CyrilXBT

CyrilXBT

84,911 Aufrufe • vor 3 Monaten

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

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

CyrilXBT

43,403 Aufrufe • vor 5 Monaten

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 Aufrufe • vor 4 Monaten

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

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

56,568 Aufrufe • vor 4 Monaten

THIS GUY CANCELLED 9 SUBSCRIPTIONS AND BUILT A SMARTER SYSTEM FOR $0 he used to pay $500 a month for 9 different apps his notes were scattered, his tasks were lost, his data belonged to someone else then he moved everything into obsidian 506 nodes, 1064 connections, one vault, zero monthly fee his information finally belongs to him bookmark this before you pay for another subscription

THIS GUY CANCELLED 9 SUBSCRIPTIONS AND BUILT A SMARTER SYSTEM FOR $0 he used to pay $500 a month for 9 different apps his notes were scattered, his tasks were lost, his data belonged to someone else then he moved everything into obsidian 506 nodes, 1064 connections, one vault, zero monthly fee his information finally belongs to him bookmark this before you pay for another subscription

leopardracer

49,591 Aufrufe • vor 5 Monaten

Boris Cherny gave Claude Code a memory that has no database, no indexing, no setup, and 80% of Anthropic runs on it a CLAUDE.md "gets automatically read into context at the start of every session" 12:48 - CLAUDE.md loads into memory every session 13:15 - Keep memory short or it burns your context 15:48 - Memory stacks from you to your whole company 17:30 - The memory command shows what Claude remembers 19:33 - Hit pound and Claude remembers it forever the whole memory layer is files → drop a CLAUDE.md in your repo and Claude reads it in on every session → nest more in subfolders and it pulls them only where it works → stack them personal to project to enterprise so one config serves the whole team → hit the pound key mid task and Claude writes the new fact into memory itself the best coding agent's memory was never a database, it was markdown you can open and edit

Boris Cherny gave Claude Code a memory that has no database, no indexing, no setup, and 80% of Anthropic runs on it a CLAUDE.md "gets automatically read into context at the start of every session" 12:48 - CLAUDE.md loads into memory every session 13:15 - Keep memory short or it burns your context 15:48 - Memory stacks from you to your whole company 17:30 - The memory command shows what Claude remembers 19:33 - Hit pound and Claude remembers it forever the whole memory layer is files → drop a CLAUDE.md in your repo and Claude reads it in on every session → nest more in subfolders and it pulls them only where it works → stack them personal to project to enterprise so one config serves the whole team → hit the pound key mid task and Claude writes the new fact into memory itself the best coding agent's memory was never a database, it was markdown you can open and edit

NO1ennn

13,015 Aufrufe • vor 2 Monaten

STOP TREATING YOUR OBSIDIAN VAULT AS AI MEMORY. WITHOUT ONE ROUTING FILE, CLAUDE IS BURNING TOKENS ON NOISE YOU FORGOT YOU SAVED. a folder full of markdown does not make Claude smart. what makes it smart is what your agent can find without rereading the whole vault. storage: write → tag → graph → agent scans everything the model touches the entire vault, hallucinates half of it, forgets by the next session. memory: write → index → route → agent opens two files the model reads the index first, follows one path, answers with a link back to the note. i have rebuilt my Obsidian vault three times this year. the first two collapsed inside a month because Claude kept guessing which folder to open. the third one holds because the first thing i ship now is the routing file. Markdown, links, and the graph view are not what changed. what changed was a one-line description per folder, written for the agent, kept current, loaded before any retrieval call. if your agent still starts every session by scanning your whole vault, you are running storage. write the routing file today.

STOP TREATING YOUR OBSIDIAN VAULT AS AI MEMORY. WITHOUT ONE ROUTING FILE, CLAUDE IS BURNING TOKENS ON NOISE YOU FORGOT YOU SAVED. a folder full of markdown does not make Claude smart. what makes it smart is what your agent can find without rereading the whole vault. storage: write → tag → graph → agent scans everything the model touches the entire vault, hallucinates half of it, forgets by the next session. memory: write → index → route → agent opens two files the model reads the index first, follows one path, answers with a link back to the note. i have rebuilt my Obsidian vault three times this year. the first two collapsed inside a month because Claude kept guessing which folder to open. the third one holds because the first thing i ship now is the routing file. Markdown, links, and the graph view are not what changed. what changed was a one-line description per folder, written for the agent, kept current, loaded before any retrieval call. if your agent still starts every session by scanning your whole vault, you are running storage. write the routing file today.

kocer

17,240 Aufrufe • vor 2 Monaten

A solo developer building an ocean ship game with Claude Opus 5.5 has shared his workflow and costs, alongside a free playable demo. → He runs a separate Claude session for each game system and talks only to a 'manager' session that messages the rest → A decisions.md file tags every choice as [USER] or [AI], with user decisions always taking priority → He uses Blender MCP and TripoAI for 3D models, Godot MCP for the engine, and Codex when Claude limits run out → He says the project cost about $800 over two months, including $600 for Claude Max Reddit:

A solo developer building an ocean ship game with Claude Opus 5.5 has shared his workflow and costs, alongside a free playable demo. → He runs a separate Claude session for each game system and talks only to a 'manager' session that messages the rest → A decisions.md file tags every choice as [USER] or [AI], with user decisions always taking priority → He uses Blender MCP and TripoAI for 3D models, Godot MCP for the engine, and Codex when Claude limits run out → He says the project cost about $800 over two months, including $600 for Claude Max Reddit:

0xMarioNawfal

49,413 Aufrufe • vor 25 Tagen

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 Aufrufe • vor 3 Monaten