Video yükleniyor...
Video Yüklenemedi
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... show more
110,968 görüntüleme • 3 ay önce •via X (Twitter)
34 Yorum

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.

the real edge is memory

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

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

Obsidian

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

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

Obsidian

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

I was just thinking the same thing

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

the skill is the easy part

this is great

Claude google ads entegrasyonu için inceleyin:

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.

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

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.

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.

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

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

Obsidian

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

Compound intelligence beats starting over.

Obsidian

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.

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

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?

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.

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 😐

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.

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.

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.

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.

Obsidian
