- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper studies why sharing past trajectories can make web agents perform worse than using no memory. The authors combine filtering successful trajectories, compressing the injected text, and retrieving experiences based on task intent, and use comparisons and ablations to show that selecting experiences matters more than simply accumulating them.
Critical strengths
The clearest strength is the extensive experimental coverage, including the full task set, multiple seeds, random and failed-memory controls, and checks with a second model and an offline environment.
Critical weaknesses
Filtering experiences, shortening memory text, and retrieving relevant trajectories are common choices in existing agent memory methods, and their combination here does not establish a clearly different approach. More importantly, the finding that irrelevant experiences can hurt while relevant ones help does not substantially advance the understanding provided by prior work. Meanwhile, this paper appears to bear strong traces of AI‑generated content, with non‑standard phrasing throughout the main text.
Questions for authors
- Which validated finding changes our understanding of experience reuse beyond AWM, ReasoningBank, and prior memory-management studies?
- Does the learned VAE index still outperform raw embeddings or random projection when the memory pool, deduplication rule, and injected text are held fixed? It is necessary to present controlled results demonstrating an independent and consistent benefit from the learned index.
- Under the definition in A.2, why is the relevant-entry rate 78% while Recall@3, defined as retrieving at least one relevant experience, is only 64%? It would be better to have an explanation regarding this point.
- Does the full method retain a meaningful benefit when historical experiences from tasks with the same official template are excluded?