- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
Rollback-Induced Reflection (RIR) coordinates when an agent should review its progress, which checkpoint it should return to, and what information should survive the rollback. The environment and branch-specific context are restored, while useful reflections are retained without preserving stale claims about the current state. The paper evaluates this recovery mechanism on ALFWorld, ScienceWorld, and GAIA with three backbones.
Critical strengths
- The separation of reusable knowledge from rollback-invalidated state is thoughtful. An agent that undoes an action but still remembers the resulting state as current can immediately repeat its mistake; the proposed memory interface addresses this failure directly.
- The presentation is good. The when/where/what organization is clear, and the component ablations help explain the design. The paper gives a reasonably concrete account of implementing restoration in the tested environments.
Critical weaknesses
- Interaction steps and auxiliary model calls do not capture the complete cost of restoration. Reset-and-replay, file snapshots, and all generated tokens can matter. The applicability to irreversible external actions is also more limited than the general agent framing suggests.
- The incremental contribution needs a stronger direct comparison. GA-Rollback already combines error detection with rollback and explicitly evaluates a GA-Rollback + Reflexion variant. Comparing RIR with the individual components does not establish an advantage over this closest existing combination.
Questions for authors
Please refer to critical weakness.
4 comments
Response to Reviewer ZH66 (Part 2 of 2)
W2: Direct comparison with GA-Rollback + Reflexion
We thank the reviewer for identifying this closely related combination. The Rollback only ablation in Tables 3, 6, and 7 retains RIR’s recovery control while withholding the reflection briefing from the acting agent. It therefore tests the incremental contribution of generator-facing reflection, but does not replace a direct comparison with GA-Rollback + Reflexion.
To address this question, we have added a direct comparison with GA-Rollback + Reflexion across two backbones and three benchmarks in Appendix D.4, together with the experimental setup and result analysis:
| Backbone | Method | ALFWorld SR (%) | ScienceWorld SR (%) | GAIA SR (%) | Avg. SR (%) |
|---|---|---|---|---|---|
| Qwen3.8-27B | GA-Rollback + Reflexion | 97.76 | 75.28 | 51.32 | 74.79 |
| Qwen3.8-27B | RIR | 99.25 | 79.70 | 50.66 | 76.54 |
| DeepSeek-V3 | GA-Rollback + Reflexion | 79.85 | 68.27 | 35.53 | 61.22 |
| DeepSeek-V3 | RIR | 94.03 | 76.75 | 37.50 | 69.43 |
RIR improves average SR by 1.75 percentage points on Qwen3.8-27B and 8.21 points on DeepSeek-V3. On DeepSeek-V3, it improves all three benchmarks, including gains of 14.18 points on ALFWorld and 8.48 points on ScienceWorld. On Qwen3.8-27B, the combination leads by 0.66 points on GAIA, while RIR leads by 1.49 points on ALFWorld and 4.42 points on ScienceWorld, retaining the higher overall average.
This additional comparison directly tests whether RIR’s advantage comes merely from having both rollback and reflection. GA-Rollback + Reflexion already includes both, yet RIR achieves higher average performance on both backbones. Together with the existing component ablations, these results support the incremental value of coordinating review timing, restore-point selection, and cross-recovery information retention, beyond using rollback and reflection alongside each other.
Thank you again for your feedback
Thank you again for your feedback. We would appreciate hearing whether our responses and additional experiments have addressed your concerns. We would be happy to clarify any remaining points.
We wanted to briefly follow up on our response, particularly the restoration-cost analysis and the added comparison with GA-Rollback + Reflexion. If you have had a chance to review these results, we would appreciate any feedback on whether they address your concerns. We would be happy to clarify any remaining points.
Response to Reviewer ZH66 (Part 1 of 2)
We thank the reviewer for the positive assessment of the presentation, restoration implementation, and cross-rollback memory design. The concerns about complete restoration costs and comparison with the closest existing combination help sharpen the assessment of RIR’s practical value. We address them below.
W1: Restoration costs and practical applicability
Cost accounting. We agree that interaction steps and auxiliary model calls alone do not fully characterize restoration cost. To provide more direct quantitative evidence, we additionally analyze the DeepSeek-V3 execution logs for the ALFWorld dataset, comparing RIR with GA-Rollback in terms of environment replay work and historical trajectory-text overhead.
For reset-and-replay, RIR reduces cumulative environment-action replay by 47.6% relative to GA-Rollback. These replays execute saved action prefixes without fresh model generation. For the historical trajectory-text component of actor inputs, we used the DeepSeek-V3 tokenizer to count the retained reasoning, action, and observation text before each invocation, removing abandoned suffixes after rollback. Under this common accounting procedure, RIR reduces the estimated cumulative trajectory-token volume from 33.13k to 16.08k per task, approximately 51.5%. Thus, this experiment provides evidence of reduced environment replay work and a smaller historical trajectory-text burden, alongside fewer auxiliary calls.
For GAIA workspace restoration, we use Git’s content-addressed object storage to share identical content across checkpoints rather than saving an independent full directory copy for each checkpoint. This design avoids duplicate storage through content reuse; actual snapshot and restoration overhead depends on workspace size and file changes.
Applicability. RIR assumes that the task provides a restorable execution interface. In ALFWorld and ScienceWorld, this is implemented through environment reset and replay of the retained action prefix. In GAIA, restoration includes the agent context and local workspace. This capability has a practical engineering basis. We have contributed functionality for selectively restoring context, memory, and workspace files to a widely used open-source agent system. RIR builds on such restoration interfaces to study how an agent can autonomously decide when to recover, where to resume, and which knowledge to retain.
We do not claim that checkpoints can undo irreversible external actions, such as an email that has already been sent. This is a general boundary of agent interaction with external systems: restoring the agent’s state does not automatically undo an action already completed outside it. Appendix C.4 now explicitly states this applicability boundary alongside the benchmark-specific restoration mechanisms.