When you automatically improve the supporting system (harness) for a large language model agent, changes that worked well in one setting often fail when you switch to a different test or model. Restarting the improvement process from scratch wastes time and repeats mistakes.
The authors created a memory that records why each change was made, what it was expected to do, and what actually happened. When the setting changes, the optimizer can consult this history to decide which fixes to keep, adapt, or drop.
In experiments across several domains, this memory approach scored higher than starting over. On coding tasks, it improved scores by an average of 2.36 points, winning in 9 out of 10 runs. This shows that keeping a structured record of past attempts makes automated system tuning more reliable when conditions shift.
