Loading video...

Video Failed to Load

Go Home

SOMEONE JUST TURNED AN IDLE CLAUDE MAX SUBSCRIPTION INTO A 24/7 AI OPS SYSTEM AT ZERO EXTRA COST. NO API KEY. NO METERED BILLING. NO CLOUD 76 cron tasks. 12 AI specialist teams. 0 additional dollars per month uses Claude Code in headless mode - claude -p - the...

chewadot's profile picture

chewa.

3,759 subscribers

68,707 views • 1 month ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch
0:24

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

chewa.

13,367 views • 1 month ago

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

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

West Lord

110,658 views • 2 months ago

Anthropic just gave OpenClaw the green light Anthropic staff confirmed that CLI-based usage is sanctioned. We’ve successfully bridged the Claude Code CLI directly into the OpenClaw gateway, letting you run your entire agent fleet on your Pro/Max plan and no additional API tokens required. The Implementation: - Auth: Log in to Claude Code locally: claude auth login - Path: Grab your binary location: which claude - Bridge: Drop the path into your openclaw.json under agents.defaults: "cliBackends": { "claude-cli": { "args": [ "-p", "--output-format", "json" ], "command": " ", "input": "arg", "output": "json", "serialize": true, "sessionArg": "--session-id", "sessionMode": "existing" } }, "model": { "primary": "claude-cli/claude-opus-4-6" }, "models": { "claude-cli/claude-opus-4-6": {}, "claude-cli/claude-opus-4-7": {}, "claude-cli/claude-sonnet-4-6": {} }, The Result: OpenClaw reuses your local session IDs and subscription limits. You get the full power of Opus and Sonnet without the restricted OAuth endpoints or the API tax. They sanctioned the path. We built the bridge. Here is a video how I done it step by step:
1:09

Anthropic just gave OpenClaw the green light Anthropic staff confirmed that CLI-based usage is sanctioned. We’ve successfully bridged the Claude Code CLI directly into the OpenClaw gateway, letting you run your entire agent fleet on your Pro/Max plan and no additional API tokens required. The Implementation: - Auth: Log in to Claude Code locally: claude auth login - Path: Grab your binary location: which claude - Bridge: Drop the path into your openclaw.json under agents.defaults: "cliBackends": { "claude-cli": { "args": [ "-p", "--output-format", "json" ], "command": " ", "input": "arg", "output": "json", "serialize": true, "sessionArg": "--session-id", "sessionMode": "existing" } }, "model": { "primary": "claude-cli/claude-opus-4-6" }, "models": { "claude-cli/claude-opus-4-6": {}, "claude-cli/claude-opus-4-7": {}, "claude-cli/claude-sonnet-4-6": {} }, The Result: OpenClaw reuses your local session IDs and subscription limits. You get the full power of Opus and Sonnet without the restricted OAuth endpoints or the API tax. They sanctioned the path. We built the bridge. Here is a video how I done it step by step:

Ziwen

182,975 views • 4 months ago

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.
20:58

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,096 views • 3 months ago

48 HOURS AFTER KARPATHY POSTED HIS LLM WIKI IDEA, A 26-YEAR-OLD BIRMINGHAM GRAD SHIPPED THE ONE COMMAND THAT MAKES IT WORK. IT NOW HAS 76,000 GITHUB STARS 1 command. 71.5x fewer tokens per query. 0 vector databases points graphify at any folder - codebase, docs, PDFs, screenshots, video. Tree-sitter parses the code, Claude reads the prose, the whole thing lands as a knowledge graph in graphify-out/ one flag - --obsidian - writes the entire graph as a fully-linked Obsidian vault: one markdown note per concept, every relationship a wikilink, every node linked back to its source. Drop the vault into Claude Code as a skill. Claude queries the graph instead of grepping through raw files, forever Safi Shamsi finished his MSc at Birmingham with Distinction in 2025. His thesis was a knowledge-graph RAG system for academic search. He shipped Graphify 48 hours after Karpathy's post, iterates every week, and has already been forked by Rootly AI Labs for incident data. Hacker News, Analytics Vidhya, Towards AI - all organic.76,000 stars. Three months old no neo4j server. no vector db. no embedding pipeline. no cloud. no monthly fee you're reading this on a device that could clone the repo, run one command, and have a Claude-native knowledge graph of your entire codebase in Obsidian before your next standup
16:36

48 HOURS AFTER KARPATHY POSTED HIS LLM WIKI IDEA, A 26-YEAR-OLD BIRMINGHAM GRAD SHIPPED THE ONE COMMAND THAT MAKES IT WORK. IT NOW HAS 76,000 GITHUB STARS 1 command. 71.5x fewer tokens per query. 0 vector databases points graphify at any folder - codebase, docs, PDFs, screenshots, video. Tree-sitter parses the code, Claude reads the prose, the whole thing lands as a knowledge graph in graphify-out/ one flag - --obsidian - writes the entire graph as a fully-linked Obsidian vault: one markdown note per concept, every relationship a wikilink, every node linked back to its source. Drop the vault into Claude Code as a skill. Claude queries the graph instead of grepping through raw files, forever Safi Shamsi finished his MSc at Birmingham with Distinction in 2025. His thesis was a knowledge-graph RAG system for academic search. He shipped Graphify 48 hours after Karpathy's post, iterates every week, and has already been forked by Rootly AI Labs for incident data. Hacker News, Analytics Vidhya, Towards AI - all organic.76,000 stars. Three months old no neo4j server. no vector db. no embedding pipeline. no cloud. no monthly fee you're reading this on a device that could clone the repo, run one command, and have a Claude-native knowledge graph of your entire codebase in Obsidian before your next standup

chewa.

299,992 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
16:36

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

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

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

Yarchi

56,177 views • 2 months ago

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

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

Spike 1%

18,223 views • 1 month ago

do you understand what Claude just did? > you can now tell Claude to use your entire computer. open apps. navigate your browser. fill spreadsheets. anything you’d do sitting at your desk > uses your connected apps first… Slack, Calendar, integrations. when there’s no connector, it asks permission to open the app on your screen directly > assign a task from your phone. walk away. come back to finished work on your computer > tell it once to scan your email every morning or pull a report every Friday and it just handles it > macOS only right now. research preview in Cowork and Claude Code > not long ago you needed a custom framework just to get Claude running on a loop. now it’s fully native → dispatch from your phone… native → scheduled recurring tasks… native → remote monitoring… native → multi-agent coordination… native → persistent memory across sessions… native every feature that made agentic frameworks valuable is becoming a platform feature for Claude the AI race just got way more interesting
0:20

do you understand what Claude just did? > you can now tell Claude to use your entire computer. open apps. navigate your browser. fill spreadsheets. anything you’d do sitting at your desk > uses your connected apps first… Slack, Calendar, integrations. when there’s no connector, it asks permission to open the app on your screen directly > assign a task from your phone. walk away. come back to finished work on your computer > tell it once to scan your email every morning or pull a report every Friday and it just handles it > macOS only right now. research preview in Cowork and Claude Code > not long ago you needed a custom framework just to get Claude running on a loop. now it’s fully native → dispatch from your phone… native → scheduled recurring tasks… native → remote monitoring… native → multi-agent coordination… native → persistent memory across sessions… native every feature that made agentic frameworks valuable is becoming a platform feature for Claude the AI race just got way more interesting

klöss

463,668 views • 5 months ago

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.
4:19

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 views • 2 months ago

ANTHROPIC JUST KILLED A DOZEN AI MEMORY STARTUPS WITH ONE BUILT IN TOOL people raised millions to give AI long term memory. Anthropic just shipped it straight into the API. free, no framework, no vector database. it is a folder of files Claude reads and writes. that is it. the trick: it is client side. Claude never touches your data directly. it only requests a file operation, and your app runs it against storage you control. before every task Claude checks its /memories directory, pulls back what it learned last time, and keeps going. when it learns something new, it writes it down. six plain operations do all of it: > view, create, str_replace, insert, delete, rename why it actually wins: > just in time retrieval, it reads on demand instead of loading everything up front > it survives a context reset, so a long job resumes instead of starting over > every path is locked to /memories, so it cannot wander your filesystem > works on every Claude 4 model, no beta flag, generally available Anthropic even pairs it with context editing and compaction, so the live window stays tiny while the important stuff lives on disk. the whole thing in one line: Claude keeps the notes, you keep the storage. bookmark this before you pay for a memory layer you no longer need.
0:26

ANTHROPIC JUST KILLED A DOZEN AI MEMORY STARTUPS WITH ONE BUILT IN TOOL people raised millions to give AI long term memory. Anthropic just shipped it straight into the API. free, no framework, no vector database. it is a folder of files Claude reads and writes. that is it. the trick: it is client side. Claude never touches your data directly. it only requests a file operation, and your app runs it against storage you control. before every task Claude checks its /memories directory, pulls back what it learned last time, and keeps going. when it learns something new, it writes it down. six plain operations do all of it: > view, create, str_replace, insert, delete, rename why it actually wins: > just in time retrieval, it reads on demand instead of loading everything up front > it survives a context reset, so a long job resumes instead of starting over > every path is locked to /memories, so it cannot wander your filesystem > works on every Claude 4 model, no beta flag, generally available Anthropic even pairs it with context editing and compaction, so the live window stays tiny while the important stuff lives on disk. the whole thing in one line: Claude keeps the notes, you keep the storage. bookmark this before you pay for a memory layer you no longer need.

NO1ennn

42,946 views • 19 days ago

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.
0:37

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

Gipp 🦅

14,871 views • 3 months ago

SOMEONE BUILT AN ENTIRE COMPANY BRAIN INSIDE CLAUDE CODE IN 7 DAYS Not Obsidian. Fully custom. A living map of every employee, every agent, every SOP on one screen. Click any node and it opens up: - what department it's in - what SOPs are attached - what it can actually access that permission layer is the whole game an employee opens the chat and the AI already knows their access level, agents, SOPs and tools surface in the conversation like you tagged them by hand Obsidian cannot do this... no dev team. no six month build. no enterprise budget. just Claude Code and one week has everything to build one full guide on building your own team below
1:20

SOMEONE BUILT AN ENTIRE COMPANY BRAIN INSIDE CLAUDE CODE IN 7 DAYS Not Obsidian. Fully custom. A living map of every employee, every agent, every SOP on one screen. Click any node and it opens up: - what department it's in - what SOPs are attached - what it can actually access that permission layer is the whole game an employee opens the chat and the AI already knows their access level, agents, SOPs and tools surface in the conversation like you tagged them by hand Obsidian cannot do this... no dev team. no six month build. no enterprise budget. just Claude Code and one week has everything to build one full guide on building your own team below

Madni Aghadi

397,151 views • 1 month ago

YOU CAN BUILD AN AI SECOND BRAIN IN 15 MINUTES. No coding experience. No $1000 course. Here is the entire setup. Step 1: Download Claude Desktop. Step 2: Download Obsidian. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect to your vault using Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude reads all of it, finds connections you missed, and surfaces insights from your own thinking that you FORGOT you had. Most people use Claude as a search engine. The people building second brains use it as an INTELLIGENCE LAYER on top of everything they know. That gap is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight. Follow CyrilXBT
1:19

YOU CAN BUILD AN AI SECOND BRAIN IN 15 MINUTES. No coding experience. No $1000 course. Here is the entire setup. Step 1: Download Claude Desktop. Step 2: Download Obsidian. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect to your vault using Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude reads all of it, finds connections you missed, and surfaces insights from your own thinking that you FORGOT you had. Most people use Claude as a search engine. The people building second brains use it as an INTELLIGENCE LAYER on top of everything they know. That gap is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight. Follow CyrilXBT

CyrilXBT

260,035 views • 1 month ago

Clude is now available as a custom connector on Anthropic Claude. Giving it persistent memory across every conversation. It remembers your projects, your preferences, and the decisions you make, so you never start from zero again. Use Clude across Chat / Co-Work and Claude Code. Add it in 30 seconds, no API key: 1. In Claude: Customize, Add custom connector URL: Enter your email. That's it. Recap for people unfamiliar: Clude deviates from the traditional vector database that many others bolt onto Claude. We are a cognitive memory system modeled on how human memory works. Think traditional memory systems: Calculator > It computes. Fullstop. Excel > Dynamic, formula run, able to share and manipulate Clude scored 86% on LongMemEval, one of the toughest long-term memory benchmarks. This means less hallucinations to traditional platforms. It scores memories by relevance, recency, and importance, links them into a knowledge graph, and consolidates them over time. Tell Claude something, open a new chat, and watch it remember.
0:39

Clude is now available as a custom connector on Anthropic Claude. Giving it persistent memory across every conversation. It remembers your projects, your preferences, and the decisions you make, so you never start from zero again. Use Clude across Chat / Co-Work and Claude Code. Add it in 30 seconds, no API key: 1. In Claude: Customize, Add custom connector URL: Enter your email. That's it. Recap for people unfamiliar: Clude deviates from the traditional vector database that many others bolt onto Claude. We are a cognitive memory system modeled on how human memory works. Think traditional memory systems: Calculator > It computes. Fullstop. Excel > Dynamic, formula run, able to share and manipulate Clude scored 86% on LongMemEval, one of the toughest long-term memory benchmarks. This means less hallucinations to traditional platforms. It scores memories by relevance, recency, and importance, links them into a knowledge graph, and consolidates them over time. Tell Claude something, open a new chat, and watch it remember.

seb

20,598 views • 2 months ago

19-year-old Vietnamese student built himself a second brain through Claude and Obsidian - and made $18,000 in his first month. Every morning Claude already knows who he is, what he's working on, which tasks are open and which ideas were captured a month ago - no reminders, no manual searching. He drops an article into a folder - Claude reads it, writes a summary, updates the index and links 10-15 related pages in one pass. Set up a cron job once at 7:30 AM - now a briefing with all his tasks and new materials is waiting before he even gets out of bed. Published the system as a course on Gumroad - $97 for access, 186 sales in the first month. Vannevar Bush described this idea back in 1945 and called it the Memex - but couldn't solve one question: who does the maintenance. Now the answer is known - Claude. And a 19-year-old student from Hanoi is already selling that answer for $18,000 a month.
5:00

19-year-old Vietnamese student built himself a second brain through Claude and Obsidian - and made $18,000 in his first month. Every morning Claude already knows who he is, what he's working on, which tasks are open and which ideas were captured a month ago - no reminders, no manual searching. He drops an article into a folder - Claude reads it, writes a summary, updates the index and links 10-15 related pages in one pass. Set up a cron job once at 7:30 AM - now a briefing with all his tasks and new materials is waiting before he even gets out of bed. Published the system as a course on Gumroad - $97 for access, 186 sales in the first month. Vannevar Bush described this idea back in 1945 and called it the Memex - but couldn't solve one question: who does the maintenance. Now the answer is known - Claude. And a 19-year-old student from Hanoi is already selling that answer for $18,000 a month.

Cortex

24,389 views • 3 months ago

A 26-year-old plugged Claude Code into his Obsidian vault and the vault started working night shifts. 9,412 notes. 6 years of reading, ideas, half-dead projects. Dead weight until 3 weeks ago. He pointed Claude Code at the vault folder. No plugins. No API glue. The vault is just markdown files, and Claude Code reads files. That's the whole trick everyone misses. Now every night at 2 AM a cron job wakes Claude inside the vault: reads the 40 newest notes links them to old ones he forgot existed writes a daily brief called "what your brain missed" drafts 3 content ideas from collisions between notes Morning 1 it connected a 2021 note on Roman logistics with a 2026 note on AI agent routing. That collision became a post. 214,000 views. Morning 9 it found a SaaS idea buried in a book summary from 2022. He built the landing page the same day. 61 signups before dinner. Morning 17 it flagged that 3 of his abandoned drafts were the same idea written 3 times. He merged them. Best thing he's shipped this year. Cost: $0 in new tools. Obsidian is free. The vault was already there. 6 years he treated his second brain like a warehouse. Turns out it was an employee waiting for a boss.
0:30

A 26-year-old plugged Claude Code into his Obsidian vault and the vault started working night shifts. 9,412 notes. 6 years of reading, ideas, half-dead projects. Dead weight until 3 weeks ago. He pointed Claude Code at the vault folder. No plugins. No API glue. The vault is just markdown files, and Claude Code reads files. That's the whole trick everyone misses. Now every night at 2 AM a cron job wakes Claude inside the vault: reads the 40 newest notes links them to old ones he forgot existed writes a daily brief called "what your brain missed" drafts 3 content ideas from collisions between notes Morning 1 it connected a 2021 note on Roman logistics with a 2026 note on AI agent routing. That collision became a post. 214,000 views. Morning 9 it found a SaaS idea buried in a book summary from 2022. He built the landing page the same day. 61 signups before dinner. Morning 17 it flagged that 3 of his abandoned drafts were the same idea written 3 times. He merged them. Best thing he's shipped this year. Cost: $0 in new tools. Obsidian is free. The vault was already there. 6 years he treated his second brain like a warehouse. Turns out it was an employee waiting for a boss.

Spike 1%

147,951 views • 1 month ago

AMD JUST KILLED THE $200 - A - MONTH AI SUBSCRIPTION - A 65-WATT BOX WITH 128GB OF UNIFIED MEMORY THAT RUNS 70B MODELS LOCALLY. that clip is amd's ryzen ai max+ 395 mini box, held up on stage. the whole pitch is one spec: 128gb of high-speed unified memory. why it matters: cpu, gpu and npu share the same 128gb pool, so a model that used to need a rack of vram just fits. what it actually runs: llama 70b in full precision on the built-in gpu open models up to ~100b parameters, locally, no cloud all of it in a mini pc pulling around 65 watts that's the part that ends the subscription: your prompts, your data, your model, on a box on your desk, not metered by the token. honest line: this runs open models, not gpt-5 or claude opus. for chat, coding help and agents on your own data it's more than enough. for the absolute frontier, the cloud still wins. and it isn't free: the box runs ~$1,500 and up. but that's a few months of a $200 sub, then it's yours forever. no monthly ai bill, no tokens metered, no prompt leaving the room. the uncomfortable part isn't that amd made a fast box. it's that "you need the cloud for ai" was a pricing choice, and unified memory just made it optional. follow RetroChainer for the hardware that turns rent into ownership, and bookmark this before your next ai renewal.
0:41

AMD JUST KILLED THE $200 - A - MONTH AI SUBSCRIPTION - A 65-WATT BOX WITH 128GB OF UNIFIED MEMORY THAT RUNS 70B MODELS LOCALLY. that clip is amd's ryzen ai max+ 395 mini box, held up on stage. the whole pitch is one spec: 128gb of high-speed unified memory. why it matters: cpu, gpu and npu share the same 128gb pool, so a model that used to need a rack of vram just fits. what it actually runs: llama 70b in full precision on the built-in gpu open models up to ~100b parameters, locally, no cloud all of it in a mini pc pulling around 65 watts that's the part that ends the subscription: your prompts, your data, your model, on a box on your desk, not metered by the token. honest line: this runs open models, not gpt-5 or claude opus. for chat, coding help and agents on your own data it's more than enough. for the absolute frontier, the cloud still wins. and it isn't free: the box runs ~$1,500 and up. but that's a few months of a $200 sub, then it's yours forever. no monthly ai bill, no tokens metered, no prompt leaving the room. the uncomfortable part isn't that amd made a fast box. it's that "you need the cloud for ai" was a pricing choice, and unified memory just made it optional. follow RetroChainer for the hardware that turns rent into ownership, and bookmark this before your next ai renewal.

RetroChainer

16,995 views • 22 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.
0:22

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

Spike 1%

58,428 views • 1 month ago

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

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

Yarchi

58,186 views • 2 months ago