- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes an approach that improves task performance through experience sharing among agents in multi-user deployments. Reusable experience acquired by one user's agent remains inaccessible to other users, while pooling memories risks transferring personal preferences. The authors introduce ShareMem, which shares only how to act and which preferences to consult. Source-specific values in experiences are abstracted into semantic slots, while concrete preference values are supplied by each user's own preference store. Experiences are first refined in a local pool by an LLM-based manager through add, replace, and remove operations, and a shared manager then independently updates the shared pool using only accepted local edits as evidence. During execution, scope-first retrieval selects local and shared experiences from closer scopes first under a joint entry budget, alongside initial and agent-initiated preference retrieval. Across Mind2Web, VitaBench 2.0, and MemoryCode with four backbone models, the authors report that ShareMem outperforms user-local memory across all backbones.
Critical strengths
-
The ShareMem design — separating shared memory and personal preferences is a reasonable structure for sharing the agent experience from other users while preserving the user's personal preferences.
-
Ablation study gives further understandings — Two-stage consolidation, which updates the shared pool using only accepted local edits rather than raw sessions, yields a more compact shared pool and substantially lower induction token usage than direct writing, while also improving downstream performance.
Critical weaknesses
-
The central premise of ShareMem remains unverified. The paper does not define what constitutes a user-specific value as opposed to reusable procedure, leaving this boundary to the LLM manager's judgment, and the separation relies solely on prompt instructions (Appendix C) without any audit of the shared pool for leaked values. Given the paper's own finding that agents misuse other users' preferences despite explicit instructions (Tables 16–17), it is unclear whether ShareMem actually prevents cross-user preference transfer.
-
The evidence for the core claim is limited. Mind2Web involves no preferences and assigns each website's data to a single user, and MemoryCode's shared pools are minimal (40, 17, and 1 entries; Table 4), leaving VitaBench 2.0 as the main test, where the gains are modest. Moreover, no results report variance or significance tests (Tables 1–3), so the reliability of these small gains is unclear.
Questions for authors
-
In the perspective of ShareMem's weakness mentioned in W2, especially for MemoryCode, shared pools contain only 40, 17, and 1 entries (Table 4), it is unclear whether sharing meaningfully contributes in this setting. How often are shared entries actually retrieved, and does ShareMem differ from LOCAL on subset 7, where only a single shared entry exists?
-
The paper offers little qualitative evidence for ShareMem itself. What fraction of shared pool entries contain values traceable to contributing users, such as the examples mentioned in Table 17? Could the authors apply the audit protocol of Table 16 to ShareMem's failures, and provide examples of extracted shared experiences, cases where ShareMem succeeds but LOCAL fails, and the types of failures that remain?