SoMem: Can LLM Agents Organize Their Own Memory?

Zichuan Fu1*, Junjia Qi1*, Wenlin Zhang1, Yimin Deng1, Shirong Wang1, Jinyang Li1, Xian Wu2, Xiangyu Zhao1†
1City University of Hong Kong2Tencent Jarvis Lab
*Equal contribution†Corresponding author

Best Reported Results

93.25% on LoCoMo · 90.20% on LongMemEval-S
Highest full-set SoMem accuracy in the manuscript's backbone and cross-model experiments.

BenchmarkLJ accuracyQuestionsWriterReader
LoCoMo93.25%1,540 (all, categories 1–4)GPT-5.6 LunaQwen 3.8 Flash
LongMemEval-S90.20%500 (all)DeepSeek V4 FlashDeepSeek V4 Flash

LoCoMo reuses frozen memory across Writer and Reader models. LongMemEval-S uses the same model for construction and answering, with up to 50 QA turns. Both use GPT-4o-mini judging; the manuscript does not explicitly specify Reader reasoning effort for these configurations. Different-model results are separate from the shared-Reader comparison.

Reader-effort experiments — fixed subsets

BenchmarkBest subset scoreQuestionsReaderRequested effort
LoCoMo95.00% LJ accuracy100GPT-6.1 SolxHigh
BEAM-100K70.83% mean nugget score200Qwen 3.8 FlashNone

These are subset scores, not full-set results. Memory and questions are reused within each sweep; the scaling tables and accompanying text do not identify the Writer. See configurations and result provenance. These manuscript results have not been rerun with the public recipes.

Example linked Topic documents: two employment events in one paragraph have separate event times and Source evidence; a paragraph reference connects the related project document.

Let the agent organize its memory

  • Ordinary documents. The agent decides what to summarize, how to group related information, and when to revise existing topics.
  • Preserved evidence. Summaries stay linked to the original interactions, keeping precise details available for later inspection.
  • Validated updates. The runtime checks edits and derives relational, temporal, and recent-memory views from accepted content.
  • Cross-model reuse. Constructed memory can be used by a different Reader model.

Linked memory documents. A Topic paragraph can contain multiple events, each with its own time and Source evidence. Paragraph references connect related information across documents.

Abstract

In most LLM agents, weights are fixed after deployment, so new information must be retained in external memory. Existing approaches often rely on predefined records and fixed organizational rules, which cannot readily accommodate evolving tasks and interactions. This raises the question: can LLM agents organize their own memory using ordinary documents?

We introduce self-organized memory (SoMem), a framework that stores memory in linked documents. The agent decides what to summarize, how to group related information, and when to revise existing topics, and every summary it produces stays linked to the original interactions as evidence. The runtime validates updates and automatically derives temporal, relational, and recent-memory views from the organized content. At query time, the agent chooses what to search and read, following document links and inspecting original evidence as needed.

On LoCoMo, BEAM-100K, and LongMemEval-S, SoMem outperforms the strongest baseline by 2.66, 3.10, and 2.00 percentage points, respectively. The constructed memory can be reused across models, and additional reasoning effort can further improve answer quality. These findings demonstrate the feasibility of agents organizing and using their own persistent memory through ordinary documents. Code is available at: https://github.com/Qi202/SoMem.

Method

SoMem framework: the Writer proposes edits, the runtime validates them and rebuilds views, and the Reader searches documents and original evidence to answer a question.
Overview of SoMem. The Writer organizes editable Topic documents while Source records preserve the original interactions. Core is a bounded document in topics/core.md, included in every query's initial context. The runtime validates updates and derives Graph, Timeline, and Recent views. The Reader decides what to search and read, following document links and inspecting Source evidence as needed. Select the figure to view the full-resolution PDF.

Shared-Reader Comparison

LoCoMo, BEAM-100K, and LongMemEval-S

Table 1. Main comparison with the shared GPT-6 Luna Reader and GPT-4o-mini judge. All memory methods use GPT-6 Luna for Writer and Reader, with no Reader reasoning effort. LoCoMo and LongMemEval-S report overall LLM-judge accuracy (%); BEAM-100K reports mean nugget score (%). These are separate benchmark metrics.

MethodLoCoMoBEAM-100KLongMemEval-S
Full Context84.2250.9265.80
A-Mem60.0650.5162.80
Mem080.3249.0072.80
MemoryOS56.2347.9653.00
Nemori72.5347.9666.40
LightMem77.9943.5474.50
E-mem86.3043.3665.20
SoMem88.9654.0276.50
Gain over strongest baseline (pp)+2.66+3.10+2.00

Evaluated on 1,540 LoCoMo category 1–4 questions, 400 BEAM-100K questions, and 500 LongMemEval-S questions. See result sources and configurations for Writer settings and additional comparisons. These are the manuscript results; the public recipes have not yet been used to rerun and verify them.

BibTeX

If you find SoMem useful in your research, please cite our paper:

@article{fu2026somem,
  title   = {Can LLM Agents Organize Their Own Memory?},
  author  = {Fu, Zichuan and Qi, Junjia and Zhang, Wenlin and Deng, Yimin and
             Wang, Shirong and Li, Jinyang and Wu, Xian and Zhao, Xiangyu},
  journal = {arXiv preprint arXiv:2611.11929},
  year    = {2026},
  eprint  = {2611.11929},
  archivePrefix = {arXiv},
  primaryClass  = {cs.AI},
  url     = {https://arxiv.org/abs/2611.11929}
}