Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

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.show more

DegenCalls

2,345 subscribers

20,104 görüntüleme • 21 gün önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 görüntüleme • 27 gün önce

$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

55,345 görüntüleme • 1 ay önce

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

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

Yarchi

58,186 görüntüleme • 1 ay önce

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.

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 görüntüleme • 1 ay önce

ANTHROPIC FOUND THE MOST EXPENSIVE PART OF AI, EVERY EMPLOYEE STARTS FROM ZERO. one person explains the project to Claude. the answer disappears inside a private chat. the next employee opens another Claude and repeats the same context. Claude Tag removes that reset. everyone in a Slack channel works with the same agent. It sees the thread, remembers relevant decisions, uses the tools assigned to that channel and leaves the output where the next person can continue. Anthropic says the internal version already creates 65% of its product team’s code. the model did not suddenly become 65% smarter. the context stopped disappearing between people.

ANTHROPIC FOUND THE MOST EXPENSIVE PART OF AI, EVERY EMPLOYEE STARTS FROM ZERO. one person explains the project to Claude. the answer disappears inside a private chat. the next employee opens another Claude and repeats the same context. Claude Tag removes that reset. everyone in a Slack channel works with the same agent. It sees the thread, remembers relevant decisions, uses the tools assigned to that channel and leaves the output where the next person can continue. Anthropic says the internal version already creates 65% of its product team’s code. the model did not suddenly become 65% smarter. the context stopped disappearing between people.

Myttle

30,317 görüntüleme • 22 gün önce

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,243 görüntüleme • 1 ay önce

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

Vaibhav Sisinty

36,560 görüntüleme • 21 gün önce

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 görüntüleme • 2 ay önce

YOUR AI IS FORGETTING EVERYTHING YOU TAUGHT IT YESTERDAY. That is why most outputs still feel generic. The people getting real leverage in 2026 fixed this with one setup: Obsidian + Claude Code. Obsidian stores your thinking. Claude Code reads the patterns. Your notes become permanent context the agent can access anytime: Daily thoughts. Projects. Ideas. Contradictions. Questions you keep returning to. Then the real unlock: Custom slash commands. `/context` loads your recent thinking instantly. `/emerge` finds hidden ideas across your notes. `/challenge` tests your beliefs against your past writing. `/trace` maps how your thinking evolved over time. One critical rule: The AI never writes to the vault. You write. The agent reads. That is what keeps the system valuable. At first it feels like note-taking. Eventually it feels like a second brain.

YOUR AI IS FORGETTING EVERYTHING YOU TAUGHT IT YESTERDAY. That is why most outputs still feel generic. The people getting real leverage in 2026 fixed this with one setup: Obsidian + Claude Code. Obsidian stores your thinking. Claude Code reads the patterns. Your notes become permanent context the agent can access anytime: Daily thoughts. Projects. Ideas. Contradictions. Questions you keep returning to. Then the real unlock: Custom slash commands. `/context` loads your recent thinking instantly. `/emerge` finds hidden ideas across your notes. `/challenge` tests your beliefs against your past writing. `/trace` maps how your thinking evolved over time. One critical rule: The AI never writes to the vault. You write. The agent reads. That is what keeps the system valuable. At first it feels like note-taking. Eventually it feels like a second brain.

Dami-Defi

41,141 görüntüleme • 1 ay önce

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

Daniel San

57,240 görüntüleme • 4 ay önce

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

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

Yarchi

140,729 görüntüleme • 1 ay önce

CLAUDE JUST TURNED OBSIDIAN INTO A BRAIN THAT NEVER FORGETS (FOR $0) Someone connected Claude straight to their Obsidian vault. Now the AI reads and writes every note they own. Every client, every idea, every project. Instant recall. Runs on Claude + Obsidian. One evening. Zero code. The numbers are insane: - Notion AI: $10/month forever - A "second brain" course: $500 to $2,000 - An assistant to organize your notes: $3,000/month - This setup: $0 - Time to build: one evening - Skill required: copy the steps The opportunity is even wilder: People sell Notion "second brain" templates for $99 to $499. You just built something better for free, and it never forgets. One free vault can hold the entire memory of your business: clients, content, SOPs, ideas. One person + Claude + Obsidian + one evening = an infinite memory that never forgets. Save and watch the clip.

CLAUDE JUST TURNED OBSIDIAN INTO A BRAIN THAT NEVER FORGETS (FOR $0) Someone connected Claude straight to their Obsidian vault. Now the AI reads and writes every note they own. Every client, every idea, every project. Instant recall. Runs on Claude + Obsidian. One evening. Zero code. The numbers are insane: - Notion AI: $10/month forever - A "second brain" course: $500 to $2,000 - An assistant to organize your notes: $3,000/month - This setup: $0 - Time to build: one evening - Skill required: copy the steps The opportunity is even wilder: People sell Notion "second brain" templates for $99 to $499. You just built something better for free, and it never forgets. One free vault can hold the entire memory of your business: clients, content, SOPs, ideas. One person + Claude + Obsidian + one evening = an infinite memory that never forgets. Save and watch the clip.

shmidt

57,347 görüntüleme • 18 gün önce

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.

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 görüntüleme • 24 gün önce

THIS GUY CONNECTED CLAUDE TO TRADINGVIEW AND CUT 200+ HOURS OF MANUAL CHART WORK 40 trades a week used to mean the same loop: open the chart, check RSI, compare EMA, write notes and wait for the next setup now Claude reads TradingView 24/7, tracks volume, indicators and price conditions while he is not even at the desk this is not a $20k trading terminal and not a quant fund setup, just one laptop, one chart and one strategy written in plain English the crazy part is not that Claude predicts the market, it is that a regular trader can remove the boring human loop from every setup ↓

THIS GUY CONNECTED CLAUDE TO TRADINGVIEW AND CUT 200+ HOURS OF MANUAL CHART WORK 40 trades a week used to mean the same loop: open the chart, check RSI, compare EMA, write notes and wait for the next setup now Claude reads TradingView 24/7, tracks volume, indicators and price conditions while he is not even at the desk this is not a $20k trading terminal and not a quant fund setup, just one laptop, one chart and one strategy written in plain English the crazy part is not that Claude predicts the market, it is that a regular trader can remove the boring human loop from every setup ↓

Gipp 🦅

55,377 görüntüleme • 1 ay önce

Claude Code is terrible at UI design and everyone knows it so this guy fixed it by building an MCP that gives Claude its own AI design tool instead of going back and forth between a design platform and your code editor, Claude now creates the designs itself and drops them straight into your codebase the MCP has full context of your existing design system and project so everything it generates actually matches what you already have. one command to set up and it installs the MCP and skill files so Claude instantly knows how to use it if you're tired of the same Inter font, purple gradient, card grid layout on every project, this is definitely worth trying

Claude Code is terrible at UI design and everyone knows it so this guy fixed it by building an MCP that gives Claude its own AI design tool instead of going back and forth between a design platform and your code editor, Claude now creates the designs itself and drops them straight into your codebase the MCP has full context of your existing design system and project so everything it generates actually matches what you already have. one command to set up and it installs the MCP and skill files so Claude instantly knows how to use it if you're tired of the same Inter font, purple gradient, card grid layout on every project, this is definitely worth trying

Om Patel

398,654 görüntüleme • 3 ay önce

Noah Brier (Noah Brier) uses Claude Code as his second brain—it’s the coolest notetaking setup I’ve ever seen. He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian (Obsidian) vault. He does it all from his phone. I had him on the show to tell us exactly how he’s pulling this off. We get into: - The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates. - The “thinking partner” that lives inside Noah’s second brain: Noah points out that in the hype around AI’s ability to write, the fact that it can read is overlooked. That’s why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away. - How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works. This episode of Every 📧’s AI & I is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain. Watch below! Timestamps: Introduction: 00:01:19 How you can do deep work on your phone: 00:04:28 Why Noah thinks Grok has the best voice AI: 00:06:14 The nuts and bolts of Noah’s Claude Code-Obsidian setup: 00:11:39 Using an agent in Claude Code as a “thinking partner”: 00:23:59 Noah’s Thomas’ English Muffin theory of AI: 00:35:07 The white space still left to explore in AI: 00:44:04 How Noah is preparing his kids for AI: 00:50:41 How he brought his Claude Code setup to mobile: 01:01:54

Noah Brier (Noah Brier) uses Claude Code as his second brain—it’s the coolest notetaking setup I’ve ever seen. He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian (Obsidian) vault. He does it all from his phone. I had him on the show to tell us exactly how he’s pulling this off. We get into: - The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates. - The “thinking partner” that lives inside Noah’s second brain: Noah points out that in the hype around AI’s ability to write, the fact that it can read is overlooked. That’s why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away. - How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works. This episode of Every 📧’s AI & I is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain. Watch below! Timestamps: Introduction: 00:01:19 How you can do deep work on your phone: 00:04:28 Why Noah thinks Grok has the best voice AI: 00:06:14 The nuts and bolts of Noah’s Claude Code-Obsidian setup: 00:11:39 Using an agent in Claude Code as a “thinking partner”: 00:23:59 Noah’s Thomas’ English Muffin theory of AI: 00:35:07 The white space still left to explore in AI: 00:44:04 How Noah is preparing his kids for AI: 00:50:41 How he brought his Claude Code setup to mobile: 01:01:54

Dan Shipper 📧

30,792 görüntüleme • 10 ay önce

THIS CS TEACHER CONTROLS 4 CLAUDE CODE INSTANCES WITH HIS EYES AND VOICE - AND THEY FIX THEIR OWN MISTAKES AUTOMATICALLY He runs 4 Claude terminals at once - no mouse, no keyboard - eye tracking highlights the window he's looking at and voice dictation sends the prompt the moment he stops talking. But the real setup is what happens inside those terminals. Claude Code has zero memory of what went wrong last session - same bug that took 20 minutes to fix yesterday will happen again tomorrow unless you configure it correctly. His CLAUDE.md grows every time Claude makes a mistake - specific rules Claude reads before touching a single line - and PostToolUse hooks auto-format and type-check every file the moment it's written. Stop hooks run tests automatically when Claude says "done" - if they fail, Claude reads the errors and keeps fixing without any manual input. Before: 45 minutes of back-and-forth per feature, same mistakes on repeat - after: 10 minutes, most of it unattended.

THIS CS TEACHER CONTROLS 4 CLAUDE CODE INSTANCES WITH HIS EYES AND VOICE - AND THEY FIX THEIR OWN MISTAKES AUTOMATICALLY He runs 4 Claude terminals at once - no mouse, no keyboard - eye tracking highlights the window he's looking at and voice dictation sends the prompt the moment he stops talking. But the real setup is what happens inside those terminals. Claude Code has zero memory of what went wrong last session - same bug that took 20 minutes to fix yesterday will happen again tomorrow unless you configure it correctly. His CLAUDE.md grows every time Claude makes a mistake - specific rules Claude reads before touching a single line - and PostToolUse hooks auto-format and type-check every file the moment it's written. Stop hooks run tests automatically when Claude says "done" - if they fail, Claude reads the errors and keeps fixing without any manual input. Before: 45 minutes of back-and-forth per feature, same mistakes on repeat - after: 10 minutes, most of it unattended.

Noisy

13,732 görüntüleme • 1 ay önce

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

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

West Lord

74,975 görüntüleme • 26 gün önce

CLAUDE CODE IS NOW FREE AND YOU CAN BUILD AN ENTIRE AI CODING SYSTEM WITH 1M CONTEXT, AGENT OS AND OBSIDIAN MEMORY WITHOUT PAYING FOR ANY OF IT. The stack gets smarter over time and costs you nothing to run.

CLAUDE CODE IS NOW FREE AND YOU CAN BUILD AN ENTIRE AI CODING SYSTEM WITH 1M CONTEXT, AGENT OS AND OBSIDIAN MEMORY WITHOUT PAYING FOR ANY OF IT. The stack gets smarter over time and costs you nothing to run.

0xMarioNawfal

51,201 görüntüleme • 1 ay önce

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Avid

336,969 görüntüleme • 1 ay önce