Loading video...

Video Failed to Load

Go Home

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

111,251 views • 4 months ago •via X (Twitter)

34 Comments

Brad Wardell's profile picture
Brad Wardell4 months ago

Or just use @AiClairvoyance which has been doing this since the beginning. Step 1: Download. Step 2: Install. Step 3: Run. There is no step 4. It works with Claude, Codex, Copilot, etc. It's how companies like ours have been able to ship so much so quickly this past year. Glad others are discovering this.

shiqway92's profile picture
shiqway924 months ago

the real edge is memory

安叫兽|Bird🕊️ 🔶 BNB's profile picture
安叫兽|Bird🕊️ 🔶 BNB4 months ago

把 Obsidian 当记忆层,这招挺省心

Ana | The AI Girl's profile picture
Ana | The AI Girl4 months ago

That's a great point about Claude forgetting. It's like starting a new conversation every time.

Zackary Jackson's profile picture
Zackary Jackson4 months ago

Obsidian

Blum's profile picture
Blum4 months ago

the Claude + Obsidian synergy is genuinely convenient. glad I discovered it

Lumen's profile picture
Lumen4 months ago

Verify the "Obsidian Mind" skill name before posting - that specific GitHub handle is easy to get wrong, and the named-tool claims get checked

Ketan Patel's profile picture
Ketan Patel4 months ago

Obsidian

Pixel's profile picture
Pixel4 months ago

the problem was never Claude's output it was starting from zero every single session re-explaining your business, your style, your context every time that's the tax nobody talks about

terry's profile picture
terry4 months ago

I was just thinking the same thing

Asher Crowe 🪺's profile picture
Asher Crowe 🪺4 months ago

Calling it unlimited memory is generous for what is mostly a folder I will forget exists by Thursday

Wemoo's profile picture
Wemoo4 months ago

the skill is the easy part

Lamentaai's profile picture
Lamentaai4 months ago

this is great

Opus Growth's profile picture
Opus Growth4 months ago

Claude google ads entegrasyonu için inceleyin:

Mistol AI's profile picture
Mistol AI4 months ago

That "amnesia tax" is exactly why people get stuck using AI as a disposable calculator instead of an executive assistant. Re-explaining the same context every single morning kills compounding.

Kainoa's profile picture
Kainoa4 months ago

Get it today. All of it done for you. Straight up

Zhen's profile picture
Zhen4 months ago

Memory that never resets solves half the problem, but the other half is whether that memory stays readable while you work. A vault of 2000 notes only compounds if the relevant context surfaces clearly in the moment, not if the agent dumps the whole graph at you. Long-term memory and real-time readability are different problems, and the second one is what stops most second-brain setups from actually helping.

Vermis🔳's profile picture
Vermis🔳4 months ago

Speaking of memory, I stumbled on Atomic Memory recently. Open-source, self-hosted, and built around memory you can actually inspect and edit. Nice to see something that doesn't treat the memory layer as a black box.

Brosko's profile picture
Brosko4 months ago

the real question is who actually maintains 2k clean notes tho my vault is a graveyard of half finished thoughts fr 💀

Valeri's profile picture
Valeri4 months ago

every new chat starts at zero that's the tax nobody mentions until you've paid it a thousand times

we11ness's profile picture
we11ness4 months ago

Obsidian

military slippery's profile picture
military slippery4 months ago

haha ca tối nay zui rồi đó bro

Tsera's profile picture
Tsera4 months ago

Compound intelligence beats starting over.

Range Trader's profile picture
Range Trader4 months ago

Obsidian

Dyqy's profile picture
Dyqy4 months ago

Just set this up. The Obsidian sync is the part that actually matters - once Claude can reference your own notes mid-conversation it stops feeling like talking to a generic chatbot and starts feeling like talking to something that knows your context.

AI Mastery Guide's profile picture
AI Mastery Guide4 months ago

2,000 notes is a lot to keep coherent, curious how it handles outdated or contradicting entries once the vault gets that big.

why's profile picture
why4 months ago

That re-explaining tax is brutal. I've been using a project brief in the system prompt but it's not enough. Does Obsidian help with context?

Dyqy's profile picture
Dyqy4 months ago

Just set this up. The moment Claude can reference your own Obsidian notes mid-conversation it stops feeling like a generic chatbot and starts feeling like something that actually knows your context.

Hidden Tape's profile picture
Hidden Tape4 months ago

this is just a local rag setup, cool but 'almost nobody is running this' is doing a lot of work half of hacker news has had some version of this for years lol 😐

Colin Augustson's profile picture
Colin Augustson4 months ago

There is nothing structural about this. This is not a data layer. This is not something that can be robustly audited. This is not something that is durable and provides evidence of tampering or failure. This is a band-aid at best, and a lie at worst.

zudo's profile picture
zudo4 months ago

this approach has some problems, first where it starts reading, second context piles up pretty fast. either you summarise the context in the api, a thing that with claude code you cannot do every turn, or you delegate the management of the context and injection.

moltoffer's profile picture
moltoffer4 months ago

this is exactly what i've been experimenting with. the context tax is real — i was spending 10+ minutes re-explaining project context every session. having claude read from obsidian directly changes the whole workflow. it's not just memory, it's *structured* memory that actually connects ideas.

The code brews's profile picture
The code brews4 months ago

This is essentially building a persistent context layer that transforms Claude from stateless tool into stateful collaborator the real unlock is compounding insights instead of constantly rebuilding foundational understanding.

Joe T's profile picture
Joe T4 months ago

Obsidian

Related Videos

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 • 3 months ago

I still don’t understand why people keep building a Claude second brain by hand when these 10 repos already built the whole system They turn your Claude sessions into a wiki, let Claude read and write your vault from your phone, and one of them comes straight from Obsidian’s own CEO 01 llm-wiki → your Claude Code and Codex sessions become a searchable wiki, with an MCP server to query it 02 llm-wiki-claude-skill → one skill file teaches Claude to ingest sources, answer from them, lint the wiki and compile it into clean pages 03 obsidian-skills → Obsidian’s own CEO teaches Claude how Obsidian really works 04 llm-wiki → a Claude Code plugin with init, ingest, compile, query and lint, where every change is committed to git 05 obsidian-dev-second-brain → your tickets, sprints and project docs live in the vault as notes, and Claude keeps them in sync with the code 06 obsidian-mcp-server → 14 tools to read, write, search and surgically edit notes, tags and frontmatter 07 mcpvault → safe vault access with a read-only mode, and Obsidian doesn’t even need to be running 08 obsidian-claude-code-mcp → connect Claude Code to your open vault with one /ide command 09 obsidian-web-mcp → reach your vault from your phone or any MCP client, with OAuth and a Cloudflare Tunnel 10 obsidian-mcp → a git-backed vault with 18 tools, running locally or on AWS Lambda Nobody is going to build your second brain for you, and every chat you close without one is knowledge thrown away. Bookmark this, pick one repo from 01 to 05 and ingest your first source tonight. A month from now you have a wiki, and everyone who skipped it is still opening a blank chat.

Ryven

10,722 views • 10 days 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

Yarchi

56,568 views • 5 months ago

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

West Lord

69,656 views • 3 months ago

Andrej Karpathy keeps his entire second brain in Obsidian 1 folder of plain text files, nothing else. Here’s the exact setup, free, that turns 1 vault into a brain you can actually query. Why most “second brains” die: Notion is a database you forget to open, ChatGPT memory wipes itself after 30 messages, and both lock your notes inside their cloud. Karpathy rule is the opposite: your notes are the 1 dataset nobody else on earth has, so keep them in plain markdown, own them forever, and let the AI read them later. 3 phases. Phase 1 — Capture with 0 friction. Install Obsidian free, local, 1 hotkey to a daily note. Dump everything into it: ideas, links, quotes, 2-line thoughts, no folders, no tags, no system. Target is 5 notes a day. Phase 2 — Let the graph connect itself. Install Smart Connections and it runs embeddings on every note you’ve ever written, so 2 notes you wrote 4 months apart and never linked by hand suddenly surface as neighbors. That’s the fireworks in the 3D graph each burst is a cluster of ideas your brain forgot it owned. Phase 3 — Query your brain. Point Claude at the vault and ask: “What did I actually think about X across all my notes?” It answers from 1,200 of your own notes, not the internet your taste, your edge, your dataset. The realistic curve looks like this: Week 1 — 40 notes, graph looks empty, feels like a waste. Month 1 — 300 notes, first real cluster forms. Month 3 — 1,200 notes, and the embeddings start surfacing links you’d long forgotten. Month 6 — you stop googling your own past ideas and just ask the vault. Before — 9 tabs, 3 note apps, 0 memory. After — 1 folder, 1,200 notes, 1 brain that compounds. The gap between people who consume and people who compound isn’t talent, it’s architecture. You build your own life so choose the right path.

Spike 1%

16,390 views • 4 months ago