In August my coding agent kept telling me that one kind of article on this site draws about four times as many comments as another. A week earlier I had corrected that number myself: with more data it was closer to two to one.
The old note was still in its memory. It sounded exactly as sure as the new one, and it kept winning, because nothing about it looked old.
That's the failure I find hardest to catch. A missing memory is loud: the agent asks, you answer, done. A stale one is quiet. It hands you a confident answer that stopped being true, and it reads like every correct answer it has ever given you.
I tried to fix it by ranking older notes lower, and that went badly.
So I'm collecting real cases for the next part of this series:
- What did your agent remember that had stopped being true? A config value, a renamed API, a decision your team reversed, a workaround for a bug that's long fixed.
- How did you notice? A failing build, a reviewer, a customer, luck?
- How long was it wrong before anyone saw it?
Short answers are welcome. The ones with a concrete example are the ones I'll learn the most from.
