- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
Harness VLA combines a frozen VLA contact primitive with a fixed set of analytic manipulation primitives. A memory-augmented LLM planner uses task-specific traces and global success/failure rules to re-ground tasks, stage the robot, invoke the VLA for contact-rich actions, and recover from failures. The paper reports strong results on LIBERO-Pro, RoboCasa365, and RoboTwin C2R, plus real-world dual-Franka demonstrations and an offline Flash Mode based on compiled task cards.
Critical strengths
-
The division of labor is intuitive: analytic primitives handle grounding, transport, navigation, and release, while the frozen VLA handles local contact-rich actions. This targets a real limitation of both monolithic VLA policies and purely analytic controllers.
-
The trace-level analyses and primitive-usage statistics make the system more interpretable than a black-box success-rate claim. Real-world examples illustrate target redirection, ordered placement, and grasp recovery without fine-tuning the VLA.
Critical weaknesses
-
The novelty over existing code-as-policy and agentic manipulation systems is not fully isolated. The central ingredients appear to be a frozen VLA exposed as a tool, a set of analytic primitives, and retrieval of successful traces plus global rules. The paper should clarify what is algorithmically new and how the memory is constructed, updated, and generalized. Also establish that the harness gains persist across different VLA backbones.
-
Task-specific memory is bootstrapped from a reference seed for each task. This is a reasonable few-shot setting, but it means the strongest benchmark results do not establish transfer to entirely new task identities without preparation. The amount of human intervention or compute needed to create and curate memory is unclear.
Questions for authors
- What is the per-task human/compute/API cost of bootstrapping Task Specific Memory and Global Memory, and which parts are generated automatically versus manually curated?
- Can the authors provide ablations for memory and planner reasoning, and test the harness with more than one frozen VLA backbone?
- What are the API cost for the runs?
- Can the real-world demonstrations be quantified with repeated trials and a direct frozen-VLA baseline under the same task conditions?