- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper investigates how action-token supervision affects the choice of whether gradients from a continuous action expert should update the VLM backbone. The authors independently vary action-token supervision and expert-to-VLM gradient flow, comparing coupled and insulated training across three training schedules in autonomous driving, with an additional evaluation in robot manipulation. The results show that action-token supervision reduces the open-loop performance gap between coupling and insulation, whereas coupling improves closed-loop driving and manipulation performance under concurrent training even when action tokens are supervised. The study provides empirical evidence that the benefits of insulation depend on the surrounding training recipe and evaluation setting.
Critical strengths
-
The paper addresses a practically important training question: whether the action expert should update the VLM, and how this choice depends on action-token supervision. By varying these factors independently within a shared architecture, particularly in the concurrent-training setting, it helps disentangle design choices that are often bundled together in existing VLA recipes.
-
The evaluation examines multiple training schedules, open- and closed-loop driving, and robot manipulation. Notably, a small open-loop difference with action-token supervision does not imply equivalent closed-loop performance: coupling still improves driving progress under concurrent training. The manipulation results provide additional evidence beyond driving, making the findings useful for selecting VLA training strategies.
Critical weaknesses
-
The evaluation does not fully establish the trade-off between improved control and preservation of VLM capabilities. Lingo-Judge measures driving-rationale quality, but does not assess broader visual-language abilities that insulation is intended to protect. Moreover, coupling does not consistently improve safety alongside route progress: under VLM-first training with action-token supervision, progress is nearly unchanged, while the off-road-or-at-fault-collision rate increases from 0.203 to 0.282. Although these limitations are acknowledged or reported, they constrain broader recommendations about the benefits of coupling.
-
The training-history comparisons do not isolate training order from differences in component-level optimization and data exposure. Despite matching total optimizer steps, the action expert receives approximately 145.5K, 197K, and 97K updates under concurrent, expert-first, and VLM-first training, respectively. In addition, the VLM-first warm-up uses different data mixtures depending on whether action-token supervision is enabled. These comparisons remain useful as evaluations of complete training recipes, but provide weaker evidence that training order itself explains the observed differences.
Questions for authors
-
Preservation of VLM capabilities: Could you evaluate the coupled and insulated checkpoints on a held-out general vision-language benchmark, ideally including the pretrained VLM as a reference? Lingo-Judge measures driving-rationale quality, but a broader evaluation would clarify whether the control gains from coupling come at the expense of capabilities that insulation is intended to preserve.
-
Progress–safety trade-off: How should the route-progress improvements be interpreted alongside the safety results in Tables 10–12? For example, under VLM-first training with action-token supervision, coupling leaves progress nearly unchanged while increasing the off-road-or-at-fault-collision rate from 0.203 to 0.282. Could you clarify which settings support a recommendation for coupling when both progress and safety are considered, and whether differences in rollout duration or termination affect these comparisons?
-
Training-history comparison: Can you provide a targeted comparison that better separates training order from component-level update budgets and data exposure, for example by extending VLM-first training to match the concurrent model’s expert-update count? Please also clarify how the different warm-up data mixtures in the VLM-first action-token-on/off conditions affect the interpretation. If such controls are unavailable, which conclusions should be understood as comparisons of complete training recipes rather than effects of training order itself?
We thank the reviewer for recognizing the practical importance and soundness of our controlled study. We address each point below.
1. Capability retention and safety
We agree that driving-rationale quality alone cannot establish broader retention. We added a seven-benchmark VQA evaluation of all twelve driving checkpoints and pre-trained Qwen (Section 4.4; Appendix F; general comment, “VQA Retention Across Training Recipes”). This complements Actions as Language [1], cited in our original Related Work, which reported poor VQA retention despite insulation and vision–language co-training.
We also agree that VLM-first training with action-token supervision does not favor coupling: progress is essentially unchanged, while off-road-or-at-fault collisions increase from 0.203 to 0.282. We challenge insulation as a default; we do not recommend coupling across all settings.
2. Interpretation of training histories
Our purpose is to test routing across commonly used MoT-VLA training strategies, not to isolate the causal effect of training order. The highest observed route progress under concurrent training is a result among evaluated recipes, not evidence that order alone explains the ranking.
As reported, expert updates differ across concurrent, expert-first, and VLM-first training (approximately 145.5k, 197k, and 97k). Within each history and token setting, coupling-versus-insulation comparisons match initialization, training data, update opportunities, and optimization schedules.
VLM-first token-on/off warm-ups change both supervision and data exposure, so that comparison cannot isolate supervision alone. The supervision–routing interaction also appears under concurrent and expert-first training with fixed training data; the VLM-first warm-up difference cannot explain those results.
3. General VQA results
Both coupled and insulated checkpoints score substantially below pre-trained Qwen on all seven benchmarks across all three training histories. Relative performance varies by benchmark and recipe; insulation scores higher in some comparisons but does not prevent substantial degradation. Many scores are near the floor, limiting sensitivity to smaller routing differences. These results do not establish equivalent retention. Full results appear in the general VQA comment and Appendix F.
4. Progress–safety tradeoffs and termination
Without action-token supervision, coupling increases progress and lowers observed off-road-or-at-fault-collision rates across all three histories. This is our clearest evidence favoring coupling on both measures.
With supervision, outcomes depend on the recipe. Concurrent coupling increases progress from 0.600 to 0.703 and lowers off-road-or-at-fault collisions from 0.248 to 0.226. Overall collision and off-road rates also decrease, although at-fault collisions are slightly higher and some tracking metrics favor insulation. Expert-first coupling increases progress but also at-fault collisions. VLM-first coupling leaves progress essentially unchanged and worsens the combined safety outcome. These results support recipe-specific decisions.
All models use the same 827 scenes and five rollouts per scene. Scoring stops at the first collision, off-road event, or 4 m deviation from the reference trajectory. Stopping rules are identical, but scored durations can differ. Safety failures affect progress; safety rates should not be interpreted as comparisons over equal driving time.
5. Matching expert-update budgets
We have not run this extension due to compute limits; each full driving run costs approximately 15,000 H100 GPU-hours. Matching concurrent expert updates would require approximately 100k additional joint steps, bringing VLM-first training to 400k total steps. This would help assess the smaller expert-update budget, but also increase VLM updates and would not isolate order alone.
Rankings across training histories compare complete recipes. Routing comparisons remain controlled within each recipe and token setting. Likewise, VLM-first token-on/off differences cannot be attributed solely to supervision because warm-up data exposure changes.
[1] Hancock et al. Actions as Language. https://arxiv.org/abs/2509.22195