- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 3
Read review
Paper summary
This paper proposes HasMem, an adaptive continuous memory framework for long-term LLM agents. It initializes memories using token embeddings from a frozen LLM and stores them in a Soft Bank. A Controller decides whether to KEEP, SHRINK, or EXPAND each memory, while a Writer re-encodes memories when their lengths change. Reader and Global are used to improve memory readout and maintain information across interactions. The framework is trained using QA supervision and memory capacity costs. Experiments show that HasMem reduces memory usage and improves lexical F1 and answer NLL in some settings. Learned memory updates also outperform rule-based re-encoding at several compression levels, although Exact Match drops on both benchmarks.
Critical strengths
- HasMem allows memory sizes to be adjusted over time and also addresses how the LLM can effectively read compressed representations. Jointly considering memory updates and readout is a useful aspect of the design. This is a useful direction for long-term LLM agents that need to manage growing interaction histories.
Critical weaknesses
- The framework has several components (Controller, Writer, Reader, and Global), making it hard to follow the overall process. I suggest adding a short overview at the beginning of Section 3.1 to explain what each component does and how they work together. A simple end-to-end example would also help readers understand the workflow.
- The paper already compares HasMem with rule-based re-encoding and some existing memory methods. However, it would be useful to include simpler baselines, such as keeping only the most recent memories (Recent-k / Sliding Window) or selecting informative tokens using methods like Selective Context [1].
- The MSC-derived dataset contains at most seven memory records per user, and the questions mainly involve simple information retrieval. Real-world agents may need to handle hundreds or thousands of interactions. It is unclear whether HasMem can maintain memory quality over such long histories.
- Although the Controller supports KEEP, SHRINK, and EXPAND, the main experiment reports zero EXPAND operations. This makes it unclear whether EXPAND is actually useful.
- HasMem improves F1 but reduces EM on both benchmarks. This raises concerns about whether compressed memories can preserve exact factual information, especially names, numbers, and other specific details.
[1] Yucheng Li, Bo Dong, Frank Guerin, and Chenghua Lin. 2023. Compressing Context to Enhance Inference Efficiency of Large Language Models. In Proceedings of the 2023 Conference on Empirical Methods in Natural Language Processing, pages 6342–6353, Singapore. Association for Computational Linguistics.
Questions for authors
- Could you provide a step-by-step example showing how a new memory is stored, updated, and used to answer a question?
- How does HasMem perform with longer interaction histories? Does repeated compression lead to information loss over time?
- Why is EXPAND never selected? Could you provide an example or experiment showing when EXPAND helps?