模型升级后智能体记忆迁移研究
Does Your Agent's Memory Survive a Model Upgrade? A Controlled Study of Memory Portability
研究揭示了智能体记忆在模型升级后的迁移问题,告诉你哪种记忆存储方式更可靠。
研究比较了四种记忆存储方式在模型升级后的表现。固定架构知识图谱(KG-fixed)在模型更换后准确度仅变化0.0004±0.0020。压缩笔记(NOTES)则表现出高度模型耦合,准确度变化达±13个百分点。检索增强生成(RAG)系统使用50/50混合索引仅获得4.96点准确度提升,远低于完全重新嵌入的11.90点提升。48个测试案例中,保留原始历史记录可在34个案例中实现90%以上的性能恢复。
Does Your Agent's Memory Survive a Model Upgrade? A Controlled Study of Memory Portability
Model upgrades are routine; memory migrations are not. An agent can keep the same memory store and still forget: a new model may interpret old notes differently, mixed embedding versions may break retrieval, and repair may fail without the original evidence. We compare memory as the same history is preserved verbatim for long-context reading (LC-RAW), divided into chunks for retrieval-augmented generation (RAG), compressed by a model into natural-language notes (NOTES), or normalized into a fixed-schema knowledge graph (KG-fixed). The study uses 48 synthetic histories with randomized answer codes, exact scoring, and two open-weight models with sub 10 billion parameters. Our measurements show that fixed-schema structures transfer reliably, with KG-fixed accuracy changing by only $+0.0004 \pm 0.0020$ following a writer swap. Conversely, compressed NOTES exhibit high model coupling, with accuracy shifting asymmetrically by $+9.91$ or $-13.28$ percentage points depending on the specific migration direction. In RAG systems, partial embedding migrations using a 50/50 mixed index capture only a 4.96-point accuracy improvement, forfeiting the majority of the 11.90-point gain achieved through full re-embedding. Diagnostic decomposition attributes 80% ($0.467 \pm 0.014$) of the NOTES accuracy deficit to information lost during initial construction, whereas retrieval failures drive 81% ($0.364 \pm 0.012$) of the RAG deficit. Finally, store-only repair of NOTES fails to reach a 90% performance recovery target in all 48 test cases, whereas retaining the raw source history enables successful recovery in 34 of 48 cases for one tested direction. These findings highlight the necessity of direction-specific migration testing, strict embedding space isolation, and the retention of source histories for memory repair.