- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
EvoRAM combines a vision-language-action (VLA) policy with an agent that writes robot control code. Successful solutions are saved as object memory (a description, a CAD model, and code), task memory (verified code), and planning memory (mainly natural-language corrections). The agent can reuse or revise this memory when solving later tasks. Using the code loop alone, it eventually solves 121 of 130 LIBERO tasks through repeated exploration. Real robot tests show bottle opening, code-based recovery from VLA failures, and camera recalibration using memory acquired during an earlier guided run.
Critical strengths
-
The paper gives concrete examples of what the agent learns and reuses. The appendices explain how object-level code, complete task programs, and planning corrections change during exploration. These examples make the memory design easier to assess than a general claim that the agent “learns from experience.”
-
The physical demonstrations show useful ways for code and VLA control to help each other. Code-based recovery completes two-layer cube stacking in 16 of 20 trials. VLA exploration also helps the code agent find a tissue-pack grasp, which then works in 8 of 10 tested orientations. These results provide useful evidence that the two forms of control have different strengths.
Critical weaknesses
-
The experiments do not separate the benefit of memory from the benefit of further attempts. On LIBERO, the agent revisits unresolved tasks while its code and memory grow. However, there is no comparison with the same agent given the same exploration budget but without memory shared across tasks. For LIBERO, the total number of attempts, runtime, and model usage are also not reported, and the paper never gives the value of the exploration budget in Algorithm 1. The 93.1% result shows that the system can acquire solutions during exploration. It does not, by itself, show how much memory speeds up learning or how reliably the final programs work when run again. The agent judged all 130 tasks solved, but 9 had actually failed, and tasks marked as solved are not revisited (Appendix F3). This makes re-running the final programs especially important. A comparison with a simpler task-code cache would also help establish the value of the proposed memory structure. This matters because prior work such as ASPIRE already builds and reuses executable skills. The paper discusses ASPIRE and argues in Appendix A1 that its memory is organized around task-level skills, but this distinction is not tested experimentally.
-
The real-world evidence is too limited to support some of the broader claims. The bottle experiment compares about two hours of exploration on a detergent bottle with 40 minutes on a different bottle using memory. Without testing that second bottle from scratch, the time difference cannot be attributed to memory alone.
Questions for authors
-
What exploration budget (B in Algorithm 1) and total resource use did the LIBERO run have? How does performance compare with memory disabled under the same budget?
-
After freezing the final memory, how reliably can the agent repeat the tasks from new starting states, as judged by the benchmark rather than the agent itself? Do later memory changes preserve earlier skills?
-
Can you test the same new bottle with and without prior memory, using repeated runs and the same exploration limits?
7 comments
Response to Reviewer sTVK (2)
W1
(2) Repeatability of Consolidated Memory
We thank the reviewer for highlighting the importance of memory repeatability. While the reported 121/130 (93.1%) on LIBERO measures successful task discovery during iterative exploration, our real-world cube-stacking experiment (Section 3.2.1) directly evaluates the repeated reuse of previously accumulated Task Memory.
Specifically, after VLA placement failures, EvoRAM retrieves and executes the previously verified code through Quick Mode (Appendix D), without additional code exploration, achieving 16/20 successful two-layer stacking trials (80%), with 5 trials further completing three-layer stacking.
To further evaluate the generalization of accumulated memory, our additional RoboDojo experiments evaluate the first 10 tasks with 5 trials under different random seeds per task, using executable memory transferred from LIBERO and previous real-world experiments. These results provide complementary evidence that accumulated executable experience can be reused across different initial states and task configurations, without prior exploration of RoboDojo tasks.
(3) Comparison with Simpler Task-Code Memory
We thank the reviewer for suggesting a comparison with a simpler task-code cache baseline.
Unlike a simple task-code cache that primarily stores complete task implementations, EvoRAM explicitly maintains reusable object-level manipulation capabilities. In our RoboDojo experiments, all transferred memory was accumulated from LIBERO and previous real-world experiments, without any prior exploration of RoboDojo tasks.
For example, in the Fasten Screws task, EvoRAM without memory fails to tighten any screws. In contrast, with accumulated memory from previous bottle-opening experiments, EvoRAM can transfer rotational manipulation capabilities to screw tightening. Although the overall task success rate remains limited, the agent successfully tightens at least one screw in all five random-seed trials. This demonstrates the potential of Object Memory to support cross-task transfer beyond direct reuse of complete task implementations.
We will conduct a controlled comparison with a simpler task-code cache baseline in future versions of our work to further quantify the benefits of structured memory.
W2. Limited Evidence for Bottle-Opening Transfer
We agree that the approximately two-hour detergent-bottle episode and 40-minute mineral-water-bottle episode do not constitute a strictly controlled speedup comparison, given the differences in object geometry and physical properties.
However, the acquired Task Memory can be directly executed for the same previously explored bottle, completing the opening procedure in approximately 10 minutes without repeating the original exploration process, as supported by the Quick Mode mechanism described in Appendix D.
Furthermore, Appendix G provides a detailed analysis of the two bottle-opening episodes, including the executable functions accumulated during the first episode and the specific components reused during the second. In particular, the agent reuses bimanual stabilization, cap-grasp constraints, repeated turning and regrasping, and separation-verification logic, while adapting the geometric parameters to the new bottle.
We appreciate the reviewer's suggestion and plan to include more comprehensive controlled transfer experiments in future versions of our work.
Response to Reviewer sTVK (3)
Q1. Exploration Budget and No-Memory Performance
As discussed in W1 (1), we conducted additional RoboDojo experiments comparing EvoRAM with and without memory under the same model, tools, tasks, random seeds, and evaluation settings. EvoRAM achieves 46.00% average accuracy with memory, compared with 26.00% without memory, representing an improvement of 20.00 percentage points and providing direct evidence of the effectiveness of accumulated executable memory in improving task performance on previously unseen tasks.
Regarding exploration resources, the exploration budget is limited to at most two hours per task, with a maximum of 200 tool-call steps, during which model API calls are made as needed for reasoning, tool invocation, execution, and failure diagnosis. We will provide more detailed statistics on API usage and wall-clock time in future versions of our work.
Q2. Reliability of Frozen Memory Across New Initial States
As discussed in W1 (2), our real-world cube-stacking experiment demonstrates repeated execution of previously accumulated Task Memory through Quick Mode, achieving 16/20 successful two-layer stacking trials without additional code exploration. Furthermore, our additional RoboDojo experiments evaluate memory transfer across 5 random seeds per task, providing evidence of generalization across different initial configurations and benchmarks. We thank the reviewer for this valuable suggestion, which helped us strengthen the evaluation of memory reuse and generalization.
Q3. Same-Bottle Evaluation With and Without Memory
As discussed in W2, the previously acquired Task Memory can be directly executed on the same bottle through Quick Mode, completing the opening procedure in approximately 10 minutes without repeating the original exploration process. Appendix G further details how the acquired bottle-opening experience is reused and adapted to a novel bottle with different geometry. We appreciate the reviewer's suggestion and plan to include additional controlled same-object transfer experiments in future versions of our work.
Response to Reviewer sTVK
Thank you for your insightful comments and helpful suggestions. We provide detailed responses to your questions below.
W1
(1) Lack of Quantitative Memory Ablations
We thank the reviewer for this valuable suggestion. To further evaluate the effectiveness and generalization of our executable memory, we conducted additional experiments on RoboDojo using memory accumulated from LIBERO and previous real-world robotic experiments.
Due to the limited time available during the rebuttal period, we evaluated the first 10 RoboDojo tasks, with 5 trials per task, using GPT-6.1 Sol with High reasoning effort. We compared EvoRAM with and without memory under the same model and experimental settings, and additionally included the reported results of other RoboDojo agents for reference. The results are presented below.
As shown in the table, EvoRAM with memory achieves 46.00% average accuracy and a score of 50.50, outperforming several reported RoboDojo agents, including EmbodiedEvo, PhysicalRSI, and GPT-6-Astra. In contrast, disabling memory reduces performance to 26.00% accuracy and a score of 30.10, representing improvements of 20.00 percentage points in accuracy and 20.40 points in score, demonstrating the effectiveness of accumulated executable experience.
More importantly, all memory used in this experiment was accumulated from LIBERO and previous real-world experiments, without any prior exploration or memory accumulation on RoboDojo. Despite the differences between the previously explored tasks and RoboDojo, the accumulated memory remains useful for solving unseen tasks. This provides evidence of cross-task transfer beyond merely reusing solutions for previously encountered task instances.
For transparency and reproducibility, we provide the detailed execution videos of these experiments in our anonymized GitLab repository: EvoRAM Experiment Videos
We acknowledge that the current evaluation covers only a subset of RoboDojo due to the limited rebuttal period. We plan to extend the evaluation to the full benchmark with 50 trials per task in a future version.