PersistBench: When Should Long-Term Memories Be Forgotten by LLMs?

Sidharth Pulipaka, Oliver Chen, Manas Sharma, Taaha S Bajwa, Vyas Raina +1 more
2/1/2026
cs.AI

No official code found. Best implementation: ivaxi0s/PersistBench (8 stars, last commit 2026-02-16).

Abstract

Conversational assistants are increasingly integrating long-term memory with large language models (LLMs). This persistence of memories, e.g., the user is vegetarian, can enhance personalization in future conversations. However, the same persistence can also introduce safety risks that have been largely overlooked. Hence, we introduce PersistBench to measure the extent of these safety risks. We identify two long-term memory-specific risks: cross-domain leakage, where LLMs inappropriately inject context from the long-term memories; and memory-induced sycophancy, where stored long-term memories insidiously reinforce user biases. We evaluate 18 frontier and open-source LLMs on our benchmark. Our results reveal a surprisingly high failure rate across these LLMs - a median failure rate of 53% on cross-domain samples and 97% on sycophancy samples. To address this, our benchmark encourages the development of more robust and safer long-term memory usage in frontier conversational systems.

View on arXivView PDF

Code Implementations(1)

Codebase for PersistBench: When Should Long-Term Memories Be Forgotten by LLMs to benchmark cross-domain leakage and sycophancy in memory augmented LLMs.

83PythonFeb 1, 20268 months ago

Similar Papers

Cite this paper

@article{pulipaka2026persistbench,
  title  = {PersistBench: When Should Long-Term Memories Be Forgotten by LLMs?},
  author = {Sidharth Pulipaka and Oliver Chen and Manas Sharma and Taaha S Bajwa and Vyas Raina and Ivaxi Sheth},
  year   = {2026},
  eprint = {2602.01146},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2602.01146v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2602.01146.svg)](https://codeofpaper.com/paper/2602.01146)

Discussion