- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
PhysEvo introduces physical recursive self-improvement (RSI) around a frozen Astra model. A task agent executes robot tasks, while a meta-agent diagnoses failures, revises tools and skills, and tests corrections, including changes to its own diagnostic tools. The evolved framework combines joint-level control, active and retrospective observation, and reusable manipulation skills. Across 42 RoboDojo tasks, retained task-specific deployment versions achieve a five-dimension average success rate of 62% on held-out layouts. Continued skill revision on AgileX PiPER yields successful executions of five real-world tasks.
Critical strengths
- Timely implementation and evaluation. The paper studies Astra-based robot manipulation soon after the model’s release. Despite the roughly three-week interval before the submission deadline, it includes an implemented self-improvement loop, simulation evaluation, and real-robot demonstrations.
- Reasonably comprehensive evaluation. The evaluation includes comparisons with VLA policies and other Astra-based approaches. It also includes a control-interface comparison, geometric-tool checks, revision case studies, and demonstrations on five real-world tasks.
Critical weaknesses
- Unreported self-improvement cost. PhysEvo’s self-improvement cost is unclear. It uses Astra for task execution, failure diagnosis, tool and skill revision, and repeated testing, but reports no token usage, model-call counts, exploration attempts, or wall-clock time. Given Astra’s cost, final success rates alone do not establish practical efficiency or scalability. The authors should report resource consumption across the full self-improvement process and show performance against cumulative cost or exploration time.
- Value of recursive self-improvement is not clearly demonstrated. Figure 5 illustrates the reuse of a self-built diagnostic tool, but provides no success-rate comparison before and after the revision. The reported results therefore leave unclear how much benefit comes from improving the improvement mechanism itself.
- Limited gains in complex manipulation. Pen-holder filling and laptop/headphone storage remain at 0% success, leaving precise placement under contact and spatial constraints unresolved in these tasks. Compared with RoboDawn, improvements on eight challenging manipulation tasks are confined to two pouring tasks. Generalization success also drops from 50% to 45%, while long-horizon success remains at 45%. These results provide limited evidence that the proposed framework improves the capabilities needed for more demanding manipulation.
Questions for authors
- Could the authors provide an example of final task-specific skills, along with evaluation configurations to facilitate reproduction of the reported results?
- On a representative task, how does PhysEvo compare with an online RL baseline (such as SimpleVLA-RL) under comparable environment-interaction budgets, in terms of success rate, runtime, and computational cost?
2 comments
Response to Reviewer ahEp (2/2): Configuration, costs, and online RL
Continued from Part 1/2: Q2 configuration, followed by Q3 and the summary.
- Evaluation Configuration: Held-out test layout IDs for the main report are Pour Balls (36/43/30), Insert Tubes (38/49/33), and Fold Clothes (35/38/47). During testing, the Task version is strictly frozen and each episode starts from a fresh state: unlike 1-shot ICL baselines (e.g., RoboDawn), we never provide a task demonstration trajectory in context—prior development experience is passed solely through retained skills and executable tools, while same-episode history remains available for closed-loop control.
Q3: What is the development cost, and how does it compare with online RL?
- Direct Answer: Below we report exact physical executions, HTTP attempts, and known token usage for the controlled study alongside historical runtime latency. Full PhysEvo and Fixed Meta have similar recorded post-branch development token counts (~132M per method across six chains).
- 1. Post-Branching Development Cost Per Method (6 chains / 18 Meta sessions per method):
| Setting | Branch Executions | Task HTTP | Meta HTTP | Total HTTP | Known Tokens | Calls Missing Token Logs |
|---|---|---|---|---|---|---|
| Reflexion-style | 28 | 2,133 | 926 | 3,059 | 131.31M (131,313,347) | 42 |
| Fixed Meta | 23 | 2,112 | 870 | 2,982 | 132.33M (132,333,166) | 30 |
| Full PhysEvo | 22 | 2,036 | 879 | 2,915 | 131.78M (131,782,233) | 21 |
-
Accounting for the Reported Comparison: The methods have similar recorded post-branch development token counts (~131–132M per method), with Full PhysEvo using the fewest branch executions (22) and HTTP attempts (2,915) (Checkpoints 0/3/6 denote protocol allowances; early-stopped chains carry forward accepted versions). Including the 6 shared initial rollouts (
663 HTTP / 13.86M tokens), 4 uninherited screening runs (328 HTTP / 7.90M tokens), 4 infra checks (4 HTTP / 84 tokens), and the 63 unique held-out test evaluations supporting all 117 main-table report slots (6,851 HTTP / 212.96M tokens; pre-outcome caching reuses identical frozen configs at zero extra API cost), the development runs and tests covered by this accounting amount to 146 physical executions (83 dev + 63 test), 16,802 HTTP attempts (including retries/failures), and 630,153,958 known tokens (439 attempts lacked token logs). -
2. Historical Episode Runtime Breakdown (15 timestamped episodes, 2,300 HTTP attempts, ~153 attempts/episode):
| Timing Component | Mean per Episode |
|---|---|
| Waiting for cloud API responses (incl. failures; mean 17.5s, P95 27.2s/call) | 44.76 min (about 85%) |
| Other startup, robot motion, and local tool execution | 7.60 min |
| Local concurrency queuing (0.78s) & logged retry backoff (4.67s) | 5.45 s |
| Total elapsed wall-clock time | 52.45 min |
- 3. Comparison with Online RL: Online RL (e.g., SimpleVLA-RL) updates policy weights via interaction, whereas PhysEvo freezes model weights and revises software resources, requiring no GPU weight-training phase (while still incurring inference and simulation costs).
Fixed Metaserves as the exact controlled baseline for our recursive claim under a shared model, starting code, and development-budget rules; while a matched online-RL comparison remains an interesting direction for future work.
Summary
Under matched starting resources and similar recorded post-branch development token counts (~132M per method across six chains), enabling Meta-resource evolution yields an average +14.44 Score (+16.7 percentage points in SR) gain over Task-only refinement and extends to deformable cloth folding. We hope these controlled results, skill excerpts, and cost accounting for the audited batch support raising your score.
Response to Reviewer ahEp (1/2): Results, mechanism, and skill
Thank you for focusing on the benefit and cost of recursive self-improvement (RSI). From a shared start, Full PhysEvo reaches 75.56 Score / 72.2% SR versus 61.11 / 55.6% for Fixed Meta, which can already revise Task skills and code. Their recorded post-branch development token counts are similar (~132M per method across six chains). Below we provide checkpoints, a deployed skill, and measured costs.
Q1: How much does improving the improvement mechanism help, including beyond pouring?
Fixed Metacan inspect images/code, run temporary analysis scripts, and persist Task changes;Full PhysEvoadditionally persists changes to Meta knowledge, tools, and workflows.Mean official Score / official SR across protocol checkpoints (evaluated on 3 held-out layouts per task):
Evaluation: All development artifacts were frozen before testing. The reported comparison uses the same three held-out layouts per task.
Q2: What does a final task-specific skill look like, and what configuration was evaluated?
pour-liquid-into-cupskill coordinates active observation, grasp verification, incremental pouring, and upright recovery through closed-loop feedback rather than a fixed open-loop sequence. Selected excerpts across its six stages are:Continued in Part 2/2: evaluation configuration, costs, and online RL.