- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes Adaptive Experience Binding (AEB), a training-free framework that explicitly controls when and how retrieved experience influences agent execution. AEB represents experience using structured applicability, satisfaction, reliability, and intervention specifications; updates these specifications from execution evidence; and dynamically selects advice, enforcement, downgrade, or release. Experiments on WebArena and SWE-Bench-Verified show improvements across two backbone models, accompanied by reductions in execution cost.
Critical strengths
-
The paper identifies a meaningful and actionable distinction between retrieving experience and controlling its influence. The controlled measurement study holds experience fixed and demonstrates complementary failures of insufficient guidance and excessive enforcement. This provides useful insight for designing memory-based agents beyond improving memory extraction and retrieval.
-
The empirical results support the practical value of the complete framework. Under shared backbones, execution scaffolds, and task budgets, AEB improves performance across two different task domains. On SWE-Bench-Verified with DeepSeek, it improves the resolve rate from ReasoningBank’s 61.2% to 83.8%, while reducing average steps from 71.9 to 31.7. The GPT-4o results also improve, and the appendix reports token and time costs including strategy-side overhead
Critical weaknesses
-
The boundary between learned binding specifications and predefined executable machinery remains insufficiently specified. Section 4.2 describes experience content and binding specifications as learned and revisable. However, Appendices A.4–A.5 indicate that candidates are constructed by the system, grounded claims use predefined claim types, semantic review accepts or rejects candidates, and runtime assessment is deterministic. These choices are reasonable, but the paper does not sufficiently explain how an evidence capsule becomes an executable condition, which features and condition compositions are supported, or which aspects can genuinely expand through experience. Table 8 provides a conceptual example rather than a complete executable record. This limits reproducibility and the precision of the learning claim.
-
The main ablation establishes the total benefit of the closed-loop system more clearly than the contribution of its individual mechanisms. In Table 5, each variant independently evolves its memory, so the difference between 83.8% and 72.6% combines immediate binding effects with subsequent changes in learned experience. The frozen-experience study in Section 3.1 is valuable, but it uses only 30 Shopping evaluation tasks and a different experience/control setup. A frozen AEB-store comparison would strengthen the explanation of how much improvement comes from adaptive runtime control versus its interaction with experience updates.
Questions for authors
-
Could you provide a complete example tracing execution evidence through candidate construction to machine-readable applicability, satisfaction, and enforcement conditions, together with the supported condition language?
-
With the same frozen AEB experience store, how do advice-only, simple rule-based dynamic binding, and the full Binder compare?