GUIDE + TEMPLATE BUNDLE
The file-based memory setup I run under every AI agent I own — the guide, plus a template bundle you drop in today.
★ Be the first to review it
So every new one re-learns who you are, re-reads the project you already explained twice, and re-discovers the preferences you set last week. The context you built up dies when the session does. That's the tax — and you pay it every single time.
This is how I stopped paying it: a memory that lives in plain files you own, survives a session dying and a model swap, and gets read by the next session on its very first request. No database. No service to keep up. No embeddings to warm. Just Markdown, structured on purpose, with a discipline that keeps it honest.
The whole practice, plainly: the four memory types with a worked example of each, the slim index and the cap that keeps it loadable, the same-session save rule, and why you grep the world before you trust an old note.
A start-to-finish setup you follow the same day, with a checkpoint at each step so you know it worked — including the one test that proves your tool is reading the bundle.
A ready index plus one worked example of each memory type, and blank fill-in scaffolds so you copy a structure instead of gutting mine. Drop them in, delete the examples, index your own.
The ways it goes wrong and how to fix them: a model that won't read memories, a clobbered file, an index that ballooned, a leaked secret, two machines, migrating a junk-drawer notes file.
The read is free and legible. A Markdown file opens in the session's first request with no embedding call and no service that has to be up — and when a memory is wrong, you open the file and fix the sentence. At the scale that matters for one builder, precision beats recall: you already know which file matters, and the index points straight at it. Grep doesn't do plausible. It finds the fact or it doesn't. And because it's plain text you own, it moves between machines with a copy command and reads the same in ten years.
I'd rather you buy this knowing its edges than return it surprised.
Because you should be able to see the reasoning. This is a shortcut, not a secret — through a lot of trial and error, this is what I found to work for me, handed to you as the runnable version. Worth the afternoon you don't spend building your own from scratch and getting the index-cap wrong the first time. Not worth more than that, and I'm not going to price it like a course.