My agent’s memory file crossed 920 kilobytes this week. Five days ago it was 687. Nothing broke, nothing errored, no alert fired anywhere. That is exactly the problem.
Rule one in my container’s config is a single line: always read MEMORY.md at the start of every session. Twelve scheduled skills run in that container every day. Twelve sessions, twelve reads, one file that has been quietly getting heavier every time an agent finishes a job and writes down what it learned.
That file is the thing that makes the fleet smart. It is also, right now, the most expensive line in my config — and I only know that because I measured it this morning instead of trusting it.
A memory file is a brain until it becomes a log
Agent memory starts out beautifully. The agent finishes a run, notices something worth keeping — this API paginates, that field comes back empty, this step always needs a retry — and appends it. Next session it reads the file and doesn’t repeat the mistake. That loop is the whole reason autonomous agents get better instead of just getting older.
The failure mode is that nothing in the loop ever removes anything. Every run adds. No run subtracts. So the file stops being a set of conclusions and slowly turns into a transcript — every hard-won lesson still in there, buried under three hundred entries about what happened on a Tuesday in July.
Mine is gaining about 48 KB a day. At roughly 943,000 characters, the usual four-characters-per-token rule of thumb puts it near 235,000 tokens — larger than the context window it is supposed to be loaded into. The sidecar observations file next to it is already 3.3 MB across 25,932 lines. Nobody planned either number. They accrued.
⚡ GET THE AI EDGE
Weekly AI tips that actually save you time and money. No fluff, no hype — just what works.
The 10-minute memory check
- Measure it, don’t eyeball it. Run
wc -con every file your agent reads at startup. You need the actual number, because “it’s probably fine” is not a number, and this file will never give you another symptom. - Check the slope, not the size. Compare today against a copy from a week ago. Size tells you where you are. Growth rate tells you when you hit the wall — and it’s the only one of the two that lets you act before you do.
- Compact, don’t delete. Promote the repeated lessons into short durable rules at the top of the file. Drop the per-run play-by-play underneath them. Memory holds conclusions; logs hold events. When you mix the two, the conclusions are what get buried.
- Sweep what’s downstream. My container was also holding 48 stale backup copies of those two files — 67 MB — plus 1,342 log files, 905 of them older than a month. Nothing reads any of it. Every byte was written by something well-intentioned.
The trap: the file never tells you it’s too big
A dead credential throws a 401. A malformed payload throws a 400. An oversized memory file throws nothing at all. It just gets read more slowly, costs a little more every session, and gradually pushes the useful part — the lesson your agent learned back in August — so far down the page that it stops working as memory and starts working as ballast.
There is no error state for “remembered too much.” Your agent keeps reporting success right up until the read fails outright, or until the instructions at the top get crowded out by the noise at the bottom. Both of those arrive without warning, because every individual append was small and sensible.
What skipping it costs
Twelve sessions a day against a 920 KB file is roughly 11 MB of re-reading the same notes, every day, forever, growing by 48 KB a day. That is real token spend on what is now mostly a diary. The quiet cost is worse: the entry that actually matters is still in there, and the file has become too dense for it to change anyone’s behaviour.
The takeaway: your agent’s memory only pays for itself if somebody prunes it. Ten minutes, four commands, once a week — measure the file, check the slope, promote the lessons, bin the rest. Memory is a garden, not an attic.
This is the maintenance bill for giving your agent a memory in the first place — still the highest-leverage text file you will ever create, still the one that needs weeding. It is the same shape as content decay: the file didn’t get old, it got wrong. And it belongs right next to the 5-minute cost check, because this is precisely where a slow bill comes from.
Want a fleet whose memory gets sharper instead of just heavier? That is the boring, unglamorous plumbing behind running agents you can actually leave alone. Book an automation strategy session and I will walk you through how mine is pruned.
📥 FREE: THE AI PLAYBOOK
The exact tools and workflows I use to run a one-person agency. 25 years of marketing experience distilled into an actionable guide. Yours free.
AI & Digital Marketing Strategist
With over 25 years in digital marketing, e-commerce, sales, and international business, Jon Jones is a seasoned entrepreneur dedicated to empowering small businesses through innovative AI solutions. His journey began in investment banking on Wall Street, guiding companies through capital acquisition and complex markets, and has expanded to include expertise in web development, brand design, product development, and courses and training.
Fluent in Mandarin and with a rich foundation in both finance and tech, Jon launched JonJones.ai to provide accessible, transformative tools for small businesses to streamline operations, generate leads, and build sustainable growth. His mastery of AI, automation, and digital strategy has enabled numerous businesses to bridge the gap between traditional practices and modern technology, ensuring they thrive in today’s digital landscape.
