- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper introduces ReCoursive, a recurrent end-to-end driving planner that performs nonlinguistic deliberation through latent critiques. A weight-shared proposer generates candidate trajectories, and a critic both scores them and returns continuous per-candidate representations. These latent critiques condition the next proposal step, creating a propose–assess–revise loop. The model is trained end to end with trajectory and assessment supervision at every deliberation step, without language reasoning traces or demonstrated corrections. At inference, metric heads rank all cumulative candidates for final selection.
Critical strengths
The paper reframes scorer-based planning as a propose–assess–revise loop and identifies the assessment-to-revision interface as the key design choice. Returning the critic’s latent representation, rather than only scalar scores, is intuitive and well aligned with the goal of nonlinguistic deliberation.
Critical weaknesses
The paper exhibits extensive traces of AI assistance.
The assessment-supervision ablation uses a common frozen no-feedback critic, but the gap already appears at depth one, before later feedback-driven revision can explain it. Removing metric losses may also change the shared scene representation during training, so the depth-six gain cannot be attributed solely to better critiques. The explicit-score feedback comparison is also ambiguous: explicit-score feedback starts higher at depth one but fails to improve, which may reflect optimization difficulty rather than a fundamental limitation of scalar feedback. Finally, the feedback-editing interventions are illustrative examples, and the authors themselves state that they do not establish reliable directional control.
Questions for authors
Missing recent SOTA baselines. The comparison tables omit several recent methods directly comparable on NAVSIM-v2 navhard/navtest and NAVSIM-v1 navtest. Could the authors clarify why the following are not included? On navhard: DriveFuture (55.5 EPDMS, rank 1 as of April 2026), GraphWorld (53.6 EPDMS), HiST-VLA (50.9 EPDMS), MomWorld, MomADv2 (39.5 EPDMS), PhysWAM (38.1/39.8 EPDMS), GeoWAM (36.6 EPDMS), 4D-WAM (35.9 EPDMS), PerceptDrive (34.5 EPDMS), RAP (39.6 EPDMS), IDOL (76.2 EPDMS stage-1). On navtest: ReDrive (90.8 EPDMS), 4D-WAM (90.6 EPDMS), GeoWAM (90.2 EPDMS), PerceptDrive (90.2 EPDMS), ManeuverFlow (90.1 EPDMS), ForeDrive (90.0 EPDMS), SparseDriveV2 (90.1 EPDMS), HiST-VLA (88.6 EPDMS), Gaze-Flow (86.7 EPDMS), DriveSuprim (87.1 EPDMS), DriveWorld-VLA (86.8 EPDMS), IDOL (89.6 EPDMS), WA-JEPA (91.7 EPDMS). On NAVSIM-v1: TOAD (94.7 PDMS), DriveSuprim (93.5 PDMS), RAP-DINO (93.8 PDMS), SparseDriveV2 (92.0 PDMS), iPad (91.7 PDMS), Gaze-Flow (91.5 PDMS), DriveFuture (90.7 PDMS), 4D-WAM (90.9 PDMS), PerceptDrive (90.4 PDMS), ManeuverFlow (90.6 PDMS), ForeDrive (89.9 PDMS), GraphWorld (90.1 PDMS), ReDrive (91.0 PDMS), DriveWorld-VLA (91.3 PDMS). On HUGSIM: WA-JEPA (HD-Score 0.4462), PhysWAM (RC 48.9 / HD-Score 35.5), TOAD.
3 comments
Part 2/2
Finally, the feedback-editing interventions are illustrative examples, and the authors themselves state that they do not establish reliable directional control.
We include the feedback-editing interventions to show that the feedback affects revisions, not for introducing a method to control the revision reliably. To quantify this beyond single scenes, we sampled 66 scenes where the ego vehicle is close to the drivable area boundary for the DAC editing, and 85 scenes with surrounding vehicles for NoC & TTC editing:
| Edit | Metric | Scenes | Success (Safety changed) | Trajectory endpoint changed > 0.1 m |
|---|---|---|---|---|
| Toward unsafe | DAC | 66 | 37 (56%) | 66 (100%) |
| Toward safe | DAC | 66 | 34 (52%) | 66 (100%) |
| Toward unsafe | NoC | 85 | 52 (61%) | 85 (100%) |
| Toward safe | NoC | 85 | 29 (34%) | 85 (100%) |
"Success" means we successfully push a safe candidate to unsafe, or push an unsafe one to safe, using the flipped donors. We note that although many edits do not change the safety label, all of them shift the trajectory endpoint by more than 0.1 m.
Q1. Missing recent SOTA baselines. The comparison tables omit several recent methods directly comparable on NAVSIM-v2 navhard/navtest and NAVSIM-v1 navtest. Could the authors clarify why the following are not included?
Baseline selection criterion: The ICLR 2027 reviewer guidelines treat papers published on or after July 17, 2026 as contemporaneous and do not require comparisons with papers available only on arXiv.
On navhard, we went further in two ways:
- Verifiable prior baselines: We included methods that, by July 17, 2026, were either peer-reviewed or had released code and weights for
navhard(LTF, LTFv6, RAP, ZTRS, DrivoR, SimScale), enabling reproducible comparisons. - Same-backbone extensions (regardless of cutoff date or code release): We also included the two recent works that directly build on our DrivoR base planner: TOAD (which refines proposals with DrivoR's scorer via CEM search) and Gigapixel-DrivoR (which adapts DrivoR through self-play rather than imitation learning).
NAVSIM-v2 vs. NAVSIM-v1: We selected benchmarks to cover 3 complementary evaluation settings (see line 299): pseudo closed-loop (NAVSIMv2), closed-loop (HUGSIM), and longtail scenarios (KITScenes-Longtail). NAVSIMv1 overlaps with NAVSIMv2 on the same nuPlan domain, while NAVSIMv2 upgrades single-stage PDMS to two-stage pseudo-simulation and richer metrics (EPDMS), so we opted for NAVSIMv2.
navhard vs. navtest:
navhard is more challenging and less saturated (SOTA methods achieve over 90 on navtest, but below 60 on navhard). Therefore we chose navhard.
For the works you suggested on navhard and HUGSIM, we applied the same criterion:
- Already included: RAP (Table 2) and TOAD (Tables 2 and 3).
- Appeared after July 17, 2026: PerceptDrive, 4D-WAM, WA-JEPA, MomADv2, GeoWAM, PhysWAM and MomWorld. PhysWAM and MomWorld appeared on arXiv after the ICLR 2027 submission deadline.
- Appeared before July 17, 2026, but neither peer-reviewed nor with released code or weights: DriveFuture, HiST-VLA, GraphWorld and IDOL.
Revisions: We have added this criterion to Appendix C.7. Although we do not compare against these works in our tables, we have cited all of them in the Related Work of the revised paper. This follows the ICLR reviewer guidelines, which do not require comparisons with contemporaneous work or papers available only on arXiv, but strongly encourage authors to cite such related work.
Dear Reviewer TfvF, thank you again for your feedback. With the discussion period closing in about 24 hours, we wanted to check whether you have had a chance to review our responses above and the revised manuscript. Please let us know if any questions remain while we still have time to reply.
Part 1/2
We thank reviewer TfvF for the constructive review and the effort invested. We are glad to address the concerns raised.
We used AI tools as described in our AI Use Statement. We reviewed all AI-assisted content and revised for a natural academic style throughout. Choices such as opening each paragraph with a bold topic sentence were deliberate to help human readers skim the paper easily.
We agree that removing metric losses might change the learned scene representation (Appendix D.2). Our results show that assessment-supervised training is associated with larger gains across recurrent revisions, but do not fully isolate the semantic contribution of assessment supervision.
Complementarily, to isolate the role of downstream planning gradients, we performed a stop-gradient ablation that retains the forward feedback interface and all assessment losses. This substantially reduces both final performance and the improvement obtained across revisions, supporting the importance of training the critic through its use in the proposer. Please see the ablation results below.
We agree that the feedback interface affects the optimization difficulty. To test this, we compared three explicit-score interfaces: logit input, an MLP projection, and the paper's affine projection. In addition, in the stop-gradient experiment mentioned above, we cut the gradient from trajectory losses to the critic. In this way, the critic is only supervised by the assessment losses, without being optimized by the trajectory losses. We found that the stop-gradient model performs similarly to the no-feedback model, indicating that effective revisions rely on the critic being trained by trajectory losses to provide guidance beyond explicit assessments.
All results below are single-seed cross-fit EPDMS on
navhard(mean [min, max] over 3 fold seeds, following the protocol in the common response above):Takeaways:
Note on evaluation convention: At bzZK and QBm8's request, Sections 4.2–4.4 now report 5-fold cross-fit EPDMS, while Table 2 keeps the standard
navhardfull-set fitting for direct comparability with published NAVSIM works (with cross-fit alongside in Table 12). Given your familiarity with the NAVSIM literature, we welcome your view on keeping both protocols.