- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents GenieMaster, an embodied continual harness for persistent multi-robot task execution. Its core component, the Embodied Execution Protocol (EEP), connects high-level agent reasoning with robot policies through capability invocation, multimodal guidance, execution feedback, and task-state continuity. The framework further incorporates asynchronous reflection and memory consolidation to improve subsequent task execution without updating model parameters. Experiments across six real-world tasks demonstrate 78.67% average success, compared with 38.83% for a dual-system baseline. Additional evaluations show improvements in unseen-object retrieval, LIBERO-Pro performance, and experience-based orchestration, alongside a 24-hour convenience-store deployment.
Critical strengths
1.The paper addresses an important challenge in embodied intelligence: connecting high-level agent reasoning with continuous robot control and persistent multi-robot task execution.
2.EEP provides a structured interface for capability invocation, multimodal policy guidance, physical feedback, and task continuity.
3.Experiments across six tasks and multiple robot platforms demonstrate substantial improvements over conventional VLA and dual-system baselines.
4.The integration of asynchronous reflection and persistent memory offers a promising approach to improving task orchestration without modifying model parameters.
Critical weaknesses
1.EEP primarily integrates established components, including hierarchical planning, tool invocation, multimodal policy conditioning, execution monitoring, and memory-based reflection. Its fundamental distinction from existing embodied-agent harnesses and hierarchical VLA systems remains insufficiently established.
2.GenieMaster differs from the dual-system baseline in agent backbone, guidance modalities, feedback mechanisms, and orchestration capabilities. Consequently, the large performance improvements cannot be attributed to EEP or continual adaptation individually.
3.The experience-learning evaluation uses only five rounds of seven trials. Performance is non-monotonic, dropping from 71.4% to 42.9% in the fourth round, and no repeated independent learning trajectories or memory-free controls are reported.
4.The capability ablation reports execution time only for successful trials, while success rates vary substantially. The reported time reductions therefore do not establish an equivalent improvement in overall task efficiency.
5.Although a 24-hour convenience-store deployment is demonstrated, quantitative evidence regarding task throughput, intervention frequency, recovery reliability, and long-term multi-robot coordination is limited.
Questions for authors
1.What is the fundamental technical novelty of EEP compared with existing embodied-agent harnesses, hierarchical VLA systems, and tool-based robotic orchestration frameworks?
2.Can the authors provide controlled ablations isolating the contributions of multimodal guidance, success/error detection, task continuity, and experience memory under the same agent and policy backbones?
3.How robust is the proposed continual adaptation mechanism across multiple independent runs, and how does it compare with memory-free reflection or fixed-memory baselines?
4.Can the authors report end-to-end execution time, agent inference overhead, failure recovery costs, and efficiency metrics averaged over both successful and unsuccessful trials?
5.Can the authors provide quantitative results from the 24-hour deployment, including completed tasks, failures, human interventions, robot utilization, and recovery success rates?
2 comments
To auhtors
Thank you for your reply. I will keep my score. I have no further questions.
We thank the reviewer for the thoughtful feedback and concrete suggestions. We address the five questions below.
Q1. Technical novelty of EEP
Thank you for this important question. GenieMaster co-designs the agent–policy guidance interface and policy training; EEP connects guidance, execution, and physical feedback.
Agent→policy. Training and deployment accommodate agent-provided visual and textual guidance, improving instruction following and zero-shot generalization to unseen products. Temporal-offset augmentation pairs earlier guidance frames with current observations to accommodate guidance latency and reuse, improving success by 9 percentage points.
Policy→agent. With model parameters fixed, feedback supports progression and recovery, while reflection adapts guidance and orchestration. Shelf-selection and waist-adjustment strategies emerge from EEP-supported execution and reflection rather than manual specification.
As foundation models advance, we hope to encourage low-level policy data collection and training designed for agentic systems, jointly optimizing the agent harness and policy.
Q2. Component ablations
Thank you for suggesting clearer ablations. Section 4.3 cumulatively evaluates tools, agent visual guidance, and control allocation. We add three ablations and planning-failure attribution; GM and Dual-system use matched policy-training conditions.
Closed-loop orchestration. Retained progress and detector-driven transitions/recovery naturally support task continuity. Replacing GM orchestration with VLM subtask updates, using the same policy, visual-guidance mechanism, and historical memory, raises planning failures from 6% to 36%. This gap highlights the limitations of the fine-tuned VLM planner in our store setting, with over a thousand SKUs and dozens of shelf locations. Correctly executing the wrong subtask need not achieve the goal.
Guidance and memory. Separate ablations retain the full GM agent and policy. Memory removal excludes historical experience but preserves current task progress; see Q3.
Q3. Robustness of continual adaptation
Thank you for this suggestion. We conducted five independent runs from the same initial memory, each spanning five rounds, with a control retaining no cross-trial memory. With 10 trials per group per round, the two groups total 500 trials across all runs, including failures and timeouts.
Success rate (%), reported as mean ± sample standard deviation across five independent runs.
Q4. End-to-end efficiency and overhead
Extending the successful-trial timings in Section 4.3 and Appendix B, including retries, the table averages execution times and VLM calls over all trials.
C5 uses 3.6 s of inference per task (2.8 s blocking execution), with 0.08 recoveries per task averaging 3.4 s each.
Q5. Quantitative results from the 24-hour deployment
24-hour outcomes. Of 264 tasks—96 retrieval, 65 restocking, 29 cleaning, 74 patrols—253 completed and 11 failed (4 retrieval, 6 restocking, 1 cleaning).
Intervention/recovery. Human intervention occurred 8 times across 6 tasks, mainly for unrecoverable floor drops. Autonomous recovery completed the affected subtask in 13/18 events (72.2%).
Utilization. Task execution, including patrols, occupied 78%/57% of the 24-hour window for A/B. A’s higher priority yields more patrol assignments when both robots are idle and no customers are present.