Capture the Shining Moment

  Two months ago I wrote about giving my AI a library — a persistent, file-based long-term memory so Claude could remember 161 conversations instead of waking up with amnesia every morning. That post was about building the thing. This one is about a problem nobody warned me about: A memory you don't tend rots faster than no memory at all. The Disease Has a Name: Entropy Here's what they don't tell you when you set up persistent AI memory. The first week feels magical. The AI remembers your projects, your preferences, the bug you fixed on Tuesday. You feel like Tony Stark. Then the rot sets in. You rename a project but the memory still points to the old path. You kill a side-project but its file lingers, and three weeks later the AI confidently references a tool you deleted. You migrate a folder from Desktop/ to Projects/ and now half a dozen breadcrumbs lie about where things live. Each individual lie is small. Collectively, they poison the well. I ran an audit this we...

The Problem Everyone Ignores Every time you open an AI assistant, it doesn't know you. It doesn't matter what you discussed yesterday, what decisions you made, what bugs you solved together. New session, blank slate. You have a brilliant colleague who gets total amnesia every morning. I've been using Claude Code for serious development work for about two and a half months now. 161 sessions. Over 6,000 message turns. Nearly 20 projects — from system architecture to WeChat mini-programs to writing a textbook. The equivalent API cost would be $5,800+. All of that context — the decisions, the reasoning, the dead ends, the breakthroughs — locked in isolated  .jsonl  files that Claude itself can never see. Then I saw Karpathy's tweet, and something clicked. Karpathy's Insight In April 2026, Andrej Karpathy shared a workflow he'd been using heavily:  LLM as knowledge base editor . Raw materials go in, the LLM "compiles" them into a wiki of interlinked  .md  f...