- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
REPAIR distills phase-specific RL specialists into a single vision-language-action policy using critic-weighted flow matching. It first trains on observations from specialist-assisted rollouts, then refines the policy on student-visited states using newly sampled specialist action candidates. Real-robot experiments show that the resulting VLA retains specialist-level task success with smoother execution, without auxiliary controllers at deployment.
Critical strengths
- Critic-weighted action targets and student rollouts address supervision quality and deployment-state mismatch.
- The real-world evaluation measures both task success and motion smoothness, with specialist training included in the adaptation rollout budget.
- The ablations support the benefits of multiple action candidates, critic weighting, and supervision on student-visited states.
Critical weaknesses
- The closest prior distillation approaches are not directly evaluated, particularly PLD, which already addresses deployment-state coverage through targeted data collection. The recorded-action cloning and data-collection ablations support REPAIR’s components but do not establish its advantage over a complete distribution-aware distillation pipeline under matched budgets.
- Training relies on manually defined critical phases and experimenter-supplied phase labels. The paper identifies the critical stages for each task but does not clearly explain how their boundaries are determined during specialist training and student-only rollouts. The required task knowledge and annotation effort leave scalability to new tasks uncertain.
- Section 6 claims that online critic updates prevent performance degradation, but provides no curves or numerical results for this comparison. Since critic scores determine the distillation targets, the benefit of updating the critic on student-visited states needs quantitative support.
Questions for authors
- How does REPAIR compare with PLD or RLDG under matched data and interaction budgets?
- How are phase boundaries identified during training and data collection, and how much manual effort is required?
- Can you provide quantitative results comparing online critic updates, a frozen critic, and uniform candidate weighting to support the claimed prevention of performance degradation?
4 comments
Phase selection, boundary annotation, and manual effort
W2 & Q2: Phase selection, boundary annotation, and manual effort
This comment explains how critical phases and their boundaries are identified in practice, what the operator does during data collection, and how much additional annotation effort the procedure requires.
Thank you for requesting these details. We have added the selection and annotation workflow to Appendix C.1 (Lines 764–774).
Selection. We execute the base SFT policy and identify recurring failure stages. Perceived difficulty can be misleading: the policy may fail to place a toy inside a drawer while reliably stacking two bowls. We therefore select phases according to observed capability gaps and leave reliably executed phases under VLA control.
Boundary annotation. An on-site operator marks phase transitions with a keypress based on task progress. During specialist training and specialist-assisted collection, this phase signal records the phase label and triggers specialist takeover. During student-only collection, the phase label identifies which specialist provides candidate actions and which critic scores them for distillation. The student alone generates the actions executed by the robot; the specialist is used only to provide training supervision.
Manual effort. Human involvement is similar in nature to FTC [3], which also uses demonstrations and human interventions. Our operator already resets the environment and initiates rollouts; phase marking is integrated into that workflow, with labels stored alongside transitions, without a separate offline annotation pass or extra personnel. For a new task, the operator inspects the base policy's failures and follows the same procedure. The new Conclusion discussion (Lines 479–481) identifies automated phase annotation as future work.
Reference
[3] Qiao, G., et al. Focus-Then-Contact: Speeding Up Robotic Contact-Rich Task Learning with Affordance-Guided Real-World Residual Reinforcement Learning. ICML, 2026.
Quantitative evidence for online critic updates
W3 & Q3: Quantitative evidence for online critic updates
This comment addresses whether the critic needs to be updated during online distillation by comparing training curves and final-checkpoint success rates against frozen-critic and uniform-weighting controls.
Thank you for requesting quantitative evidence. We have added running-success curves and final-checkpoint evaluations (Figure 13 and Table 9, Lines 1143–1171). Each final checkpoint is evaluated over 30 trials on Dual-Arm Peg Insertion:
| Variant | Final-checkpoint success rate |
|---|---|
| Online critic updates (REPAIR) | 100% |
| Frozen critic | 83.33% |
| Uniform candidate weighting | 93.33% |
Figure 13 shows that REPAIR reaches and sustains a 100% running success rate during training, whereas the frozen critic improves but continues to exhibit failures despite extended training. The final-checkpoint results show that specialist candidates provide useful supervision even with uniform weights. Uniform weighting's advantage over the frozen critic suggests that outdated value estimates can impair supervision; REPAIR's higher success supports updating the critic as the student visits new states.
Dear Reviewer Foqp,
Thank you again for your thoughtful review. As the discussion deadline approaches, we would appreciate your feedback on whether our revisions and additional evidence address your concerns. If you feel that we have resolved your concerns, we would sincerely appreciate your consideration of a higher score.
Thank you for your time and consideration.
Best regards,
Submission 38706 Authors
Distinctions from PLD/RLDG and complete-pipeline comparisons
Thank you for recognizing the value of the supervision design, real-world evaluation, and ablations. Your requests helped us strengthen the baseline comparisons and document phase annotation and critic updates more clearly.
W1 & Q1: Distinctions from PLD/RLDG and complete-pipeline comparisons
This comment clarifies how REPAIR differs from PLD and RLDG in state collection and action supervision, and addresses the request for complete-pipeline comparisons under matched data and interaction budgets.
Thank you for highlighting this comparison. In the revised manuscript, we have added complete-pipeline comparisons and a recorded-action SFT control on Drawer and Table Clearing, under matched data and interaction budgets (Appendix D.1, Lines 1033–1060; D.2, Lines 1082–1107). The key methodological differences are:
The new Tables 7–8 report:
Why a single recorded-action SFT control? RLDG and PLD both clone recorded actions. For the same VLA and training buffer, they share this SFT procedure. After comparing their complete pipelines in D.1, we apply this common objective to successful REPAIR-collected trajectories in D.2.
Under the shared SFT objective, REPAIR data outperform both baselines' own data, supporting richer task-relevant state coverage near critical phases. Full REPAIR further reaches 100% on both tasks, supporting the benefit of its action supervision. These new comparisons complement the original component ablations (Tables 2–3, Lines 444–454), which hold observations fixed when comparing action targets and hold action supervision fixed when comparing collected states.
References
[1] Xu, C., Li, Q., Luo, J., and Levine, S. RLDG: Robotic Generalist Policy Distillation via Reinforcement Learning. arXiv:2412.09858, 2024.
[2] Xiao, W., et al. Self-Improving Vision-Language-Action Models with Data Generation via Residual RL. ICLR, 2026.