What an agent should remember, and what it should forget

Description and use

<p>By Andrew Pyle</p> <p>The first time I ran an agent across more than one session on the same project, I hit the flaw immediately: it woke up knowing nothing. Every session it re-derived the same facts about my stack, re-asked the same questions, re-made the same wrong assumptions I'd corrected the day before. It was like working with a brilliant colleague with no ability to form a memory — impressive in the moment, exhausting over a week.</p> <p>The obvious fix is to give it a memory. The non-obvious part, the part that took me a while, is that the value of a memory is almost entirely in wh

Problem

<p>By Andrew Pyle</p> <p>The first time I ran an agent across more than one session on the same project, I hit the flaw immediately: it woke up knowing nothing. Every session it re-derived the same facts about my stack, re-asked the same questions, re-made the same wrong assumptions I'd corrected the day before. It was like working with a brilliant colleague with no ability to form a memory — impressive in the moment, exhausting over a week.</p> <p>The obvious fix is to give it a memory. The non-obvious part, the part that took me a while, is that the value of a memory is almost entirely in wh

Outcome

<p>By Andrew Pyle</p> <p>The first time I ran an agent across more than one session on the same project, I hit the flaw immediately: it woke up knowing nothing. Every session it re-derived the same facts about my stack, re-asked the same questions, re-made the same wrong assumptions I'd corrected the day before. It was like working with a brilliant colleague with no ability to form a memory — impressive in the moment, exhausting over a week.</p> <p>The obvious fix is to give it a memory. The non-obvious part, the part that took me a while, is that the value of a memory is almost entirely in wh

Evidence

What an agent should remember, and what it should forget

Source