Giving AI a Library: How I Made Claude Remember 161 Conversations
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...