The Story
I asked an AI to protect my memory of it
Every serious Claude Code session builds up something you can't get back by re-reading old messages: a working memory of your project — the decisions, the dead ends, the little preferences it picked up about how you like things done. Weeks of that. Not stored in your head. Stored in a folder.
One evening I asked it a question that had nothing to do with code: "if I uninstall you, or reformat this PC, is all of that just... gone?"
That's a strange thing to sit with. We back up photos we'll never look at twice, and leave the actual thinking — the part that took real time to build — completely unprotected. So I didn't ask for a backup script. Scripts are things you trust blindly and never open. I wanted something I could actually look into — see what was really in there, drag it around, understand what was junk and what mattered, before I'd trust it with something this personal.
What came back wasn't a script. It was a living mesh — every chat, every memory file, every project rendered as a node you can grab and pull, with a whole physics simulation making the connections between them feel real. Something you'd actually open just to look at, the way you'd flip through old photos, except this is a photo of what an AI has learned about how you think.
Once it existed, the obvious next question was: why stop at one tool? Cursor, VS Code's Copilot Chat, Ollama — every one of them is quietly keeping the same kind of folder, with the same complete silence about what happens if you lose it. So AIBackup grew a tab for each one, auto-detecting whichever you actually have installed.
There's a small loop closed in how this got built, too — see the note at the bottom about vibe coding. The tool that protects an AI's memory of you was, itself, built almost entirely by talking to one.