- Rating
- 3
- Confidence
- 4
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
LLM agents often get stuck in long-horizon tasks, repeating unproductive actions until the budget runs out. PMR improves recovery by providing a corrective next step when agent got stuck. It splits past trajectories into two kinds of local evidence: where the agent was stuck (context) and which actions produced useful effects (effect). These can come from different episodes, including failed ones, and are compiled offline into conditional recovery records. On ALFWorld, TextCraft, and BabyAI, PMR achieves the highest task success while using fewer actions and model calls than memory-based baselines.
Critical strengths
-
The paper is clear and well-motivated. Its key idea is that “where the agent got stuck” and “what action helped” can be learned separately, so useful steps inside failed episodes can still be reused instead of being discarded.
-
PMR has strong results on all benchmarks, achieving higher results while using less tool calls.
-
This paper has extremely careful ablation and intervention designs, these go far beyond what most agent memory papers provide.
Critical weaknesses
-
I think it is unclear whether the gains actually come from evidence linking. The paper claims that connecting past experiences, including failed ones, to the current situation helps agents recover. However, Table 2 shows that removing the direct-effect branch reduces PMR from 77.6% to 55.0%, close to retrieval alone (56.5%). In contrast, removing information recovery only reduces performance by 3.7 points.
-
The paper lacks a baseline that uses the same interface without past experience. PMR uses a manually designed adapter that already provides useful information like task goals and progress detection. However, the baselines do not have access to this interface. A simple rule-based agent using the same information, but without any past experience, might already perform well.
Questions for authors
I have only one question: How does a rule-only controller perform when it uses the same PHI, the adapter that provides the useful information but no compiled experience?
5 comments
Response to Reviewer y7SH (2/3): Same-interface rule controls
Same-interface rule controls — Weakness 2 and your question.
We conduct this baseline on ALFWorld, the environment underlying the Table 2 ablation motivating your concern, so that the same-interface comparison can be interpreted alongside the existing execution and support interventions. Specifically, we evaluated two controls on the same 134 unseen ALFWorld tasks, using the same frozen Qwen3-4B-Instruct-2507 policy and 50-action budget:
-
PH (policy + human rules) uses the same adapter and bounded execution framework, with manually specified rules for delivery/placement, heating, cooling, cleaning, resource/hand management, and information search. For instance, the rules cover the following cases:
- Delivery / placement: if the target is held and a valid placement location is observed, move there and place it.
- Heating / cooling / cleaning: if an object must be heated, cooled, or cleaned, go to the corresponding appliance and apply the action once the object is held and the appliance is reachable.
- Resource / hand management: if the hand holds an object that is not immediately needed, put it down before another pickup or action.
- Information search: if the target object has not yet been observed and repeated actions produce no new information, systematically open unexplored receptacles (such as cabinets, drawers, or the fridge) rather than repeating the same action.
PH retains the frozen policy as the default proposer, and manual rules may replace that proposal after current-state prerequisite checks. PH uses and reads no experience artifacts. This matches PMR's execution split. The question concerns the shared adapter without compiled experience, so the proposer stays fixed; removing the policy would change the proposer as well as the experience store.
-
PMH (PH + memory) keeps those rules and adds retrieved advice from the mixed300 cards and index compiled by PMR (the same cards and index used by the PMR reference in this comparison). Retrieved experience advises the policy, while corrective overrides remain governed by the manual rules.
The new PH/PMH controls are compared with the mixed300 PMR reference from the original submission (Tables 8 and 10). Each configuration has three runs:
| Controller | Successes out of 134 | Success rate, mean ± SD |
|---|---|---|
| PH | 86 / 92 / 88 | 66.17 ± 2.28% |
| PMH | 93 / 96 / 91 | 69.65 ± 1.88% |
| PMR | 104 / 96 / 98 | 74.13 ± 3.11% |
The shared-interface rule controller is effective, reaching 66.17%. PMR reaches 74.13%, 7.96 percentage points above PH, and it is ahead on every run (104/96/98 versus 86/92/88).
PMH adds the same mixed300 cards and index, while the manual rules keep the override: the retrieved cards only advise the policy. Success moves from 66.17% to 69.65% (+3.48). Those cards therefore add little when they keep this advisory role and the manual rules retain the authority to replace the submitted action. The existing mixed300 retrieval-only arm disables recovery and keeps the cards as advice. It succeeds on 57/66/63 tasks (46.3%), so this source experience does not by itself produce PMR's result. PMR gives compiled evidence authority to replace the proposal and reaches 74.13%, 4.48 points above PMH, where the manual rules still hold that authority.
In this experiment, many different rule sets are possible, and no single set constitutes a unique baseline. To more thoroughly test the contribution of the interface, when designing the rules, we considered variants that differ in two practical respects: (1) whether resource/hand-management rules are included (placing a held object before picking up another), and (2) the information-search strategy (systematic opening of unexplored receptacles versus only retrying recent actions). We adopted the version that includes both, as these address frequent sources of stalled progress in ALFWorld. We also note that the comparison is not fully symmetric. The human rules require the designer to already identify which situations lead to stalled progress and to specify appropriate corrective actions in advance. In contrast, PMR starts from raw interaction traces with no hand-specified recovery rules and compiles conditional recovery opportunities using evidence from both successful and unsuccessful episodes.
Under this setting, PMR still outperforms both PH and PMH. Thus, the benefit extends beyond both manual rule control and supplementing that control with retrieved experience. The third comment examines the role of the supporting evidence directly through the fixed-executor support-removal interventions.
Added: Section 4.3, “Same-interface rule controls” (p. 8), and Appendix F.2 / Table 8 (p. 37) define PH/PMH and report their per-run outcomes alongside the existing mixed300 PMR reference. In the revised PDF, blue marks text that existed in the original submission and was moved or lightly edited; red marks text that is new or substantively changed.
Response to Reviewer y7SH (3/3): Execution and relevant evidence
Execution utility and evidence linking — Weakness 1.
The direct-effect branch has the largest configuration-level impact in Table 2: removing it reduces success from 77.6% to 55.0%, near retrieval alone at 56.5%. Information recovery is one execution branch; removing it leaves context-linked chains and the separately supported direct-effect branch intact. Its 3.7-point decrement measures the contribution of that branch, rather than the contribution of all evidence linking. Direct effects can intervene when a supported goal effect is applicable, whereas information recovery requires stagnation.
Two interventions distinguish execution utility from dependence on relevant evidence:
- Hold the bank fixed and change execution (Table 4). Full PMR and direct-effect-off share compiled support, cards, and the retrieval index. Enabling direct-effect execution raises mean success from 60.70% to 74.13% in the mixed300 cohort: 13.43 percentage points with the available evidence held fixed.
- Hold execution capabilities fixed and change support (Figure 3b). At 22 checkpoints, the executor and effects are fixed and retrieval is off. Removing matching support reduces escapes from 22/22 to 5/22; removing an equal amount of unrelated support preserves 22/22. This identifies the contribution of relevant evidence beyond having an executor or retaining a particular volume of support.
The deployed-event intervention corroborates this result: across 17 matched continuations, relevant-support removal reduces task success from 14/17 to 5/17, while equal-size unrelated removal preserves 14/17 (Figure 3c).
Together, these results explain why the large direct-effect ablation is consistent with the value of evidence linking: compiled evidence supports recovery through corrective execution. The information-branch ablation removes one recovery route; it does not remove all evidence-supported recovery. When execution capabilities remain fixed, removing relevant support sharply reduces recovery, whereas removing equally much unrelated support does not. The gains therefore depend on which experience supports the intervention, beyond the availability of an executor or the amount of stored experience. Combined with the same-interface rule controls in the preceding comments, these findings indicate that the improvements come from compiling and grounding relevant local evidence rather than from the shared interface or recovery framework alone.
Added: Section 4.3, “Configurations and purpose” and “From components to mechanisms” (pp. 8–9), connects branch utility to the support interventions. Appendix F.1.2 (p. 36) states the retained branches.
Reference: The intervention results discussed above are those reported in the original submission; the revision clarifies how they complement the component comparisons.
We appreciate your recognition of PMR’s central idea and the care taken in the experimental design. Your question motivated the additional same-interface controls and a clearer explanation of how the existing interventions distinguish execution utility from the contribution of relevant experience.
Response to Reviewer y7SH (1/3): Overview of our response
Thank you for recognizing the separation of context and effect evidence, the benchmark results, and the care taken in the intervention designs. We particularly appreciate your close reading of the ablations.
We address your concerns in the following two comments: