- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes ARGO-VLA, a framework for improving frozen VLA policies in laboratory manipulation tasks. The method combines a lightweight residual policy for correcting VLA actions with a trust gate that limits corrections to familiar states. It also introduces a calibrated novelty monitor that can disable residual corrections and trigger escalation when anomalies are detected. At the protocol level, an LLM-based state machine handles planning, validation, execution, and recovery. The authors evaluate the approach on AutoBio and their proposed AnomalyBio benchmark, showing promising results in action correction and multi-step protocol execution.
Critical strengths
-
The paper addresses an important problem in VLA-based robotic control, especially for laboratory tasks where small action errors can lead to failure. I like the idea of correcting a frozen VLA with a lightweight residual policy rather than fine-tuning the entire model. The separation between low-level correction and high-level orchestration is also well motivated.
-
The use of conformal prediction to control false escalations is mathematically grounded, and the paper clearly discusses the assumptions and limitations of the resulting guarantee.
-
This paper offers a benchmark built on the AutoBio simulator for failure detection and recovery in laboratory protocols.
Critical weaknesses
-
Runtime efficiency: The method introduces additional components, including DINOv2 features, kNN-based gating, anomaly monitoring, and LLM orchestration. I'm wondering how much extra runtime overhead these components introduce. Could the authors report the end-to-end inference latency and computational cost compared to the original frozen π0? This would help clarify whether the method is practical for real-time robotic control.
-
Limited analysis of residual correction errors and generalization: While the paper reports improvements in task success rates, I'd like to see a more detailed analysis of how much the residual actually reduces action or positioning errors, especially for precision-sensitive tasks. I'm also curious whether these improvements generalize to tasks with different failure modes. Additionally, could the authors analyze whether correction errors or state deviations accumulate over longer task horizons?
-
The anomaly detection guarantee is relatively limited: While the conformal calibration provides a bound on false escalations for nominal successful skill calls, it does not guarantee reliable failure detection or necessarily apply after replanning. The reported detection rate is only 52% for monitor-reachable injected failures. Could the authors analyze how the detection rate changes under different anomaly types, severities, and longer protocols? I think this would give a clearer picture of the practical reliability of the monitor.
-
Lack of direct comparisons with existing residual correction methods: I appreciate the detailed ablation studies, but they mainly show how the proposed components affect the overall system. The paper discusses several related residual correction methods, without directly comparing against them under the same experimental setting. I think such comparisons are important for establishing the benefit of the proposed method over existing approaches. It would also be helpful to evaluate the original frozen π0 checkpoint on the same episodes used for the residual methods.
Questions for authors
See in Weaknesses.
Thank you for the detailed review and constructive feedback. We address the concerns following the reviewer's numbering.
W1. Runtime and computational overhead
We measured the runtime of individual components to quantify the computational overhead of our approach. The π0 policy query takes 745 ms on an NVIDIA GB10 using float32 inference, with shared GPU resources and network communication. Without GPU sharing, the query time decreases to 470 ms.
The additional components introduce only 36 ms of overhead per action chunk, approximately 4.9% of the π0 query time, primarily from DINOv2 feature extraction (36.0 ms). The monitor itself requires only 0.003 ms per control step, making its computational overhead negligible compared to policy inference.
The high-level LLM is invoked 31 times per protocol on average, including planning and recovery/replanning calls.
W2. Residual correction performance and magnitude
Using the same base-policy checkpoint, residual correction improves success on both evaluated tasks:
W4. Comparison with other residual methods
ResiP and Policy Decorator were not included in our experimental comparisons yet, but are doing them and will attach them.