- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
Previous:
FluxMem studies memory-structure selection for agents: different query types favor different memory organizations (flat, episodic, semantic), and a learned selector picks the structure per query. Experiments across dialogue-memory benchmarks and backbones report gains over fixed structures. However, no oracle or fixed-structure upper-bound control is provided, the selector's own accuracy is never reported, and some baselines (ZEP 7.92, Mem0 27.35) are far below publicly reported numbers.
Updated:
FluxMem selects linear, graph, or hierarchical organization for memory units during updatint the memory. It combines this with a three-level memory and fusion operations. The proposed method is evaluated on benchmarks like personamem and LoCoMo. Therefore, some of my orginal review about per-query selection was incorrect.
Critical strengths
Previous:
Valuable perspective:Treating memory structure as a learnable, per-query choice is a sensible extension of the memory-system design space. Complete implementation and coverage:A full pipeline (selector + multi-structure store) evaluated across benchmarks and backbones.
Updated:
The added controls provide clear evidence for learned selection. For example, the proposed method achieves 51.20 F1, versus 46.12 of the state-of-the art method. The selector itself is cheap without additional LLM calls.
Critical weaknesses
Selector contribution never isolated:Without oracle or fixed-structure controls, gains cannot be attributed to selection itself; selector accuracy is unreported. Abnormal baselines, insufficient ablations:ZEP/Mem0 baselines are far below public reproductions; missing ablations and significance tests weaken credibility.
Update:
The selector in FluexMem report 0.75 accuracy with only four test decisions. This result is still limited for the generalization. Besides, the cross dataset results are useful,while the robustness to changes in future query-type proportions is not measured.
Questions for authors
- What is the selector's accuracy and the oracle upper bound? How much gain survives selection errors?
- Why are the ZEP/Mem0 baselines far below published numbers (version, config, protocol)?
- What overhead does the selector add (LLM calls, latency)?
- Is the selection policy stable under shifts in the query-type distribution?
A gentle reminder for discussion
Dear Reviewer hNRr,
Thank you for your constructive comments and suggestions.
We have addressed your concerns by (1) clarifying FluxMem’s contribution in learning per-unit memory organization from downstream outcomes and using lightweight, distribution-aware BMM fusion; (2) adding end-to-end comparisons against random and feature-based selection, which FluxMem outperforms by 12.65 and 5.27 F1 points, respectively; (3) reporting a controlled threshold sweep, where BMM exceeds the best tested fixed threshold by 7.11 F1 points; and (4) explaining the efficiency results in Tables 7 and 10–12, including the 39% latency reduction with a 1.14-point F1 loss and the lowest reported latency in the other two evaluated settings.
The contribution clarifications and additional experimental comparisons have been incorporated into the revised manuscript, with changes marked in blue. Our efficiency response refers to measurements already included in the original submission.
We would appreciate your feedback on whether these explanations and results address your concerns. We would be happy to clarify any remaining questions.
Best regards,
The Authors of Submission 36391