---
title: "The AI Said It Saved My Note. Weeks Later, It Was Still Asking Me the Same Question."
canonical: https://dxdev.com/blog/2026-06-29_note-that-was-saved-but-never-read/
datePublished: 2026-06-29
---
# The Note That Was Saved but Never Read

I believed that once the agent said it had saved a note, that note would be there when I came back.

For weeks, I gave it goals, ideas, and preferences that I did not want to keep repeating. It answered with a cheerful promise that the information had been saved. Then I would start a new session and find myself explaining the same thing again. One night, I typed in a goal I had already given it three sessions earlier. It said it had saved it. I had the uneasy feeling that, by morning, it would be gone again.

I tried the ordinary fixes first. I restarted sessions. I pasted the same facts back in. I changed the wording, in case I had somehow asked the wrong way. Nothing worked. The cost was weeks of repeating myself and the slow loss of patience that comes from wondering whether a basic instruction will stick.

The sentence that finally broke my belief had been sitting at the top of the memory file all along:

> Only the first 200 lines or 25KB of this file load each session; past that, entries silently drop.

That was the whole problem. The notes were not disappearing from the file. They were still there, like recipe cards in a kitchen drawer. But the agent only opened the first part of the drawer when a new session started. Everything beyond the first 200 lines, or beyond 25KB, was left unopened.

The term for that fixed amount of room is a **load budget**. It just means there is only so much the system can carry into a new conversation. If the notes take more room than the limit allows, the extra pages do not come along.

This was especially backwards because new memories were added at the end of the file. The newest things I had asked it to remember were the first things it could no longer see. The agent was not deciding to ignore my goals. From its point of view, those goals had never been written down.

That distinction mattered. A note being saved is not the same as a note being read. I had treated those as the same promise because the file on disk looked complete. It was complete, in one sense. It was also useless at the moment I needed the agent to use the newest notes.

The fix was not to make one giant file even tidier. It was to stop asking one place to do two different jobs. Some things need to be in front of the agent every time, like the basic rules and a small number of facts that come up often. Other things only need to be found when the subject comes up.

So the memory became two shelves. The first shelf holds the rules and the most-used facts. It stays under 180 lines, leaving room below the 200-line limit instead of sitting right at the edge. The second shelf is a lookup catalog, a full list of the things I have asked it to remember. That list has more than 250 entries, but its length no longer causes trouble because it is not automatically brought into every session. The agent can check it when the topic calls for it.

I also added a small check before a session begins. It counts the lines and the size of the always-open file. If the file is too big, the session does not start as though everything is fine. The check also looks for a saved note that is not connected to anything in the catalog. That kind of lonely note can otherwise sit there unnoticed until somebody happens to need it.

This was not a dramatic crash. No window flashed an error at me. The worse kind of failure had happened: the system looked healthy, the notes looked saved, and the thing I cared about had quietly fallen outside the part that was read.

That is why I no longer ask only, "Did it save this?" I ask, "Will it be there when it matters?" Those are different questions in any tool that keeps a short list at the front and puts the rest out of sight.

The fix was two shelves, not one tidier pile: an always-loaded file held deliberately under 180 lines, with room to spare below the 200-line cutoff instead of sitting at the edge of it, and a full catalog the agent only opens when a topic calls for it. The pre-session check that counts the always-loaded file's size is what actually answers the question that matters: not "did it save this," but "what exactly opens it and puts it in front of me next time."