- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper presents Agency at the Right Scale (ARS), a bimanual robot-agent architecture combining task-level planning, contract-bounded local visual correction, and offline skill consolidation. Physical wrist-camera movements acquire evidence, while delegation and return determine which goals and arm roles remain fixed. On a selected RoboDojo subset, ARS reports good performance.
Critical strengths
Separating task commitments from local corrections provides a clear design for preserving goals and arm roles while allowing escalation when the arrangement must change. Integrating physical view acquisition into this interface makes the architecture practically meaningful for occluded bimanual manipulation.
ARS improves both reported metrics in every task group. The insertion example also makes the observation-to-correction mechanism concrete, while explicitly distinguishing single-tube seating from full-task success.
Critical weaknesses
W1. The promised online-ARS observation and scale-selection ablations lack quantitative success-rate/decision-step results. Table 1 compares complete configurations. It seems that the benefits of adaptive delegation and active observation are not isolated from other interface differences. This leaves the central architectural claims insufficiently validated.
W2. Table 1 omits episode counts, per-task outcomes, and uncertainty estimates. Appendix B names priors, authored procedures, environment patches, and grasp-attachment settings without specifying their exact configuration or clearly tying them to the baseline.
W3. Examples from two tasks, without trial counts or full-task success rates, do not establish cross-embodiment generalization. Section 4.4 also says an Opus 5 controller was retained from simulation, whereas Table 1 identifies GPT-6. The relationship between these configurations is not explained.
Questions for authors
Where are the observation/scale ablation results referenced in Section 4.1? Please provide success-rate and decision-step comparisons against no-active-observation and fixed-delegation variants, with APIs, skills, physical-action budgets, and seeds matched.
Which priors, procedures, patches, and grasp-attachment settings were shared with Robocurve?
Which skills were generated from traces, and were evaluation layouts held out from skill construction? For Figure 4, what are the task set, trial counts, paired success rates, and offline construction/validation cost?
Which controller, prompts, and skills were used for each simulation and physical condition? Please reconcile the GPT-6/Opus 5 descriptions and report physical trial counts, completion criteria, and full-task outcomes for both tasks.