- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
The authors introduce an Everyday Object Navigation benchmark which includes a static set and a dynamic set. They also propose EONav, a training-free VLM agent built on STRIVE that adds three key features: support-anchored temporal memory to track target-support sightings, a VLM-guided planning agent for revisiting supports or prioritizing relevant frontiers, and active verification before stopping or committing detections to memory.
Critical strengths
-
Reproducible Benchmark Construction and Realistic Problem Framing. The paper targets a key gap in everyday object navigation by benchmarking three combined challenges: revisiting relocated objects, inspecting tight spaces for small targets, and managing long-term memory updates. The dataset construction is rigorous and reproducible.
-
Validating Experiments with Performance Gain. Cross-episode temporal memory drives the dynamic search performance, more than doubling success rates while holding the exploration and verification stack constant. The results support maintaining multi-record histories rather than overwriting past sightings, which helps recover targets that return to earlier locations.
Critical weaknesses
The ablations don’t explain where the gains come from
- It is difficult to tell what actually drives EONav’s performance gains over STRIVE. Even with all support-guided features turned off, EONav still beats STRIVE by over 11 points in static search (52.14% vs. 40.71%), suggesting the gap may stem from using a stronger model stack (Gemini 3.7 Flash, GroundingDINO, SAM) rather than the proposed method itself.
- Key components are either unablated (active verification) or provide negligible gains (the frequency/recency prior), while basic control baselines are missing, such as simply revisiting the nearest known support first. To validate the claims, I would suggest to evaluate STRIVE on the same model stack, active verification needs a isolated ablation, and statistical noise should be tested, as several reported 1–3% ablation differences seem to fall within normal single-run VLM variance.
Questions for authors
- Which VLM and detector does STRIVE use in your runs, and what does STRIVE score with gemini-3.7-flash?
- What is SR/SPL with active verification removed?
- What exactly does the w/o-memory ablation remove, and why does the no-history subgroup score 47.65 when the ablation scores 23.26?
- How are pre-existing scene instances of the target category handled at evaluation?
- Fig. 11 (ep. 0403) shows the agent stopping at a pre-existing bowl-like scene object and being scored as a failure. Do HM3D scenes contain native instances of the target categories? If so, are those excluded at placement time, or counted as valid goals? Otherwise category-level successes may be scored as failures.