Introducing LightNav-0
Scaling Real2Sim2Real for Zero-Shot Generalist Navigation
Building embodied foundation models capable of zero-shot generalization across diverse robot embodiments, tasks, and scenes requires post-training (or alignment) on large-scale real-world experience. Real-world teleoperation is a primary method for collecting such experience, but reaching sufficient scale and diversity to enable zero-shot generalization remains difficult.
We create a Real2Sim2Real data engine to synthesize simulation-based surrogates for real-world experience at scale. It turns 2,000+ internet-sourced real-world scenes into reusable simulated worlds, yielding 4,000+ hours of diverse vision-language-action experience for navigation post-training.
We use this data to train our generalist navigation model through three stages: Embodied Reasoning (ER) mid-training, Embodied Supervised Fine-Tuning (SFT), and Online Reinforcement Learning (RL). The result is LightNav-0, a single model that achieves state-of-the-art performance across 10 simulation settings spanning instruction following, object-goal navigation, and embodied visual tracking, and transfers zero-shot to humanoid, quadruped, aerial, and wheeled robots.
At Light Origins, we believe the path toward Physical AGI runs through three scaling paradigms: scalable pre-training, scalable alignment, and scalable deployment. With LightNav-0, our first step toward scalable alignment through Real2Sim2Real, we demonstrate that alignment at scale is key to achieving zero-shot generalization in the physical world.
Turning real scenes into scalable experience.
Embodied post-training has a production problem. Physical experience arrives one robot, one environment, and one attempt at a time, while generalization depends on combinations of bodies, worlds, and tasks. Collecting those combinations in the real world is not only expensive; it is too slow for the iteration cycle that modern model training requires.
Scalable Alignment starts with 2,000+ internet-sourced real-world scenes. Rather than treating them as static assets, the data engine brings different scene formats into one simulation interface, where each world can support many goals, routes, viewpoints, and task formulations. Camera geometry varies with the experience, so the training distribution is not tied to one field of view, mounting height, or robot body.
Each rollout becomes one aligned record of what the model saw, what the instruction referred to, where it should attend, and how it should move. That alignment—not rendering volume alone—is what turns scene scale into post-training value. The current engine produces 4,000+ hours of vision-language-action experience; physical deployment then reveals which scenes, tasks, and interactions the next cycle should add.
Three stages of post-training.
Embodied foundation models increasingly follow a familiar post-training recipe: domain mid-training, supervised fine-tuning, and reinforcement learning. The progression is deliberate—mid-training shapes the representation, SFT teaches the behavior, and RL improves outcomes under the policy’s own distribution. LightNav-0 adapts this recipe to navigation through ER mid-training, Embodied SFT, and Online RL.
Reason about space before acting in it.
Robot trajectories are expensive because each must align a scene, an instruction, and a sequence of actions. Yet much of what a navigation policy needs before acting—grounding language in pixels, locating free space, reasoning about spatial relations, and tracking change—can be learned from images and video at far greater scale. Stage I builds these spatial priors during mid-training; Stage II uses trajectories to connect them to action.
Gemini Robotics1 is built on Gemini Robotics-ER, while MolmoAct22 uses MolmoER as its VLM backbone—two examples of embodied reasoning becoming the foundation for action learning. LightNav-ER plays that role for LightNav-0 by initializing Stage II with spatial priors. Before action alignment, it ranks first on four and second on four of the eight embodied-reasoning benchmarks we report3, with a macro-average of 67.4.
- Image pointing
- 35.14%
- Single-image VQA
- 25.05%
- General visual & abstract reasoning
- 20.00%
- Video reasoning
- 19.81%
35.14%Pointing is the largest
specialized component
67.4 average
4 first
4 second
+4.3 over initialization
Entity grounding
Grounded phrases stay linked to their image-space points.
Turn scenes into aligned embodied experience.
Stage I gives the model a spatial prior; Stage II has to turn it into behavior. Physical collection cannot cover enough combinations of scenes, goals, routes, and viewpoints at post-training scale. Real2Sim2Real changes the unit of scale: capture a scene once, then use it to produce many executable interactions.
Molmo2 annotates open-set objects.
Across every scene source, image-space points are lifted through metric depth into one target inventory.
The simulator generates executable rollouts.
It samples a target and visible start, plans the route, anchors the stop, and renders egocentric video — at scale.
VLMs turn the rollout into verified language.
Template or video-VLM drafts are rewritten under semantic checks, then verified against the final views.
ONE ROLLOUT→ONE CONSISTENT MULTIMODAL RECORD
A scene is not supervision by itself. The engine identifies what can be reached, generates routes that can actually be executed, renders them from varied egocentric views, and writes language from the completed interaction. This order matters: the instruction describes behavior that exists, rather than asking a planner to recover behavior from prose written in isolation.
After alignment and balance checks, every episode leaves the engine as one synchronized record of language, visual history, image-space points, and motion. Stage II scales these records—not scenes or videos alone, but aligned embodied experience.
An internet-sourced scene asset does not arrive with usable navigation goals. For unlabeled Gaussian splats, Molmo24 points to candidate objects in rendered views; the engine lifts those points into 3D and keeps only targets that agree across viewpoints. Scenes with annotated 3D boxes enter directly. Once a target is grounded, the engine plans and renders a route, then asks Seed2.05 to describe that specific journey. The route is fixed before language is generated, so the instruction describes a path that is physically executable in the scene.
Different reconstruction formats enter through different annotation paths, then converge on one target representation.
- Sample navigable viewpoints.
- Render RGB + metric depth in four headings.
- Use Molmo2 for open-vocabulary pointing.
- Lift points into 3D and merge across views.
Ground-truth boxes bypass visual discovery and are converted directly to the common target representation.
Object geometry projects back into the agent view; navigable space supplies the affordance target.
Once a target survives that gate, geometry supplies the route and video supplies the observation history. Language is the uncertain component, so the engine generates it along two independent paths and verifies it twice. This is what turns a rendered rollout into an aligned training example.
The action trajectory is generated first. Language is added without being allowed to change its target or geometry.
Eight directional sectors produce a target-aware template.
Seed2.0 drafts a video-grounded instruction.
One language surface for both sources.
INSIGHT-Bench documents one reproducible slice of this engine: 53,090 training episodes from 1,683 scenes, plus a frozen evaluation split of 1,097 episodes from 210 scenes. The scenes mix conventional meshes with Gaussian-splatting reconstructions; the episodes mix five kinds of spaces with five distinct ways an instruction can identify its goal.
The renderer also treats sensor geometry as a data axis. Within the same scene, it samples a 90–130° field of view, a camera height of 0.5–1.5 m, and a pitch of −15° to 15°. This exposes the policy to body-scale viewpoint changes during training instead of binding every route to one camera rig.
Source diversity changes appearance. The diagnostic taxonomy changes the spatial problem the instruction asks the policy to solve.
- HM3D / MP3D
- 34,531 65.0%
- InteriorGS
- 8,534 16.1%
- HabitatGS
- 5,776 10.9%
- VLNVerse
- 4,249 8.0%
Scene labels describe function and layout. Instruction labels come from the geometric proof used to instantiate the target, not from keywords after generation.
Make spatial reasoning executable.
These aligned records are where Stage I’s spatial prior becomes behavior. From the same language goal and visual history, the model learns three linked decisions: what the goal refers to, where motion is possible, and which trajectory reaches it. Because all three are supervised by the same interaction, Stage II learns perception and action as one problem rather than separate tasks.
The training mix preserves that foundation: most examples teach navigation and action, while a smaller reasoning stream keeps Stage I’s spatial capabilities active. With Stage II data held fixed, LightNav-ER improves every evaluated setting (Figs. 05–06). A compact interface carries this prior into behavior—image-space Point CoT exposes spatial intent, while RVQ motion tokens express the trajectory that follows.
The full Stage II mixture goes beyond this documented slice: sixteen navigation sources are co-trained with 33 reasoning sources. R2R6, RxR7, ScaleVLN8, and SRDF9 enter the stream alongside tracking data, outdoor scenes, and Gaussian-splatting worlds. The instructions remain long-form: 742K total, 474K unique, with a median length of 20 words. Fig. 05 shows how optimization is allocated; the next section shows how the geometry already present in each aligned episode becomes point supervision.
The Stage II training mix.
- Navigation + action examples
- 77.6%
- Visual question answering
- 22.4%
ER improves all eight settings.
Routes teach where to look and move.
Because the Real2Sim2Real engine retains the referred object, camera pose, and route for every frame, each episode also supplies its own point labels. A reachable future waypoint projects to an affordance point; whenever the referred object enters view, its 3D target projects to an object point. Point supervision therefore grows with the generated routes—without a separate annotation pass.
A navigable point selected from free space.
The referred object, grounded in image space.
3D BBOX
Point CoT began with a constraint: reasoning for autoregressive control must be cheap enough to run at every step and structured enough to supervise at data-engine scale. We first considered textual CoT. It is expressive, but variable in length, costly to decode, difficult to synthesize consistently, and hard to falsify when an action fails. We also considered metric 3D targets. They are precise, but tie supervision to depth, pose, camera calibration, reconstruction, and a common coordinate system across embodiments.
Image-space points offered a simpler alternative. Each decision adds only two point tokens: an object point grounds the referred object when it is visible, and an affordance point identifies free space for progress. Simulation geometry supplies both labels at scale. At deployment, the model predicts them from RGB and language—without depth, localization, calibration, or a map. Because the format is fixed, the reasoning sequence stays short.
Fig. 08 tests whether this compact reasoning signal changes the learned policy. With everything else held fixed, Point CoT improves all eight settings, raising mean SR by 8.4 and mean SPL by 5.7.
Point CoT improves all eight settings.
- MEAN SR
- +8.4
- MEAN SPL
- +5.7
- SETTINGS IMPROVED
- 8 / 8
Motion as tokens.
Each training target is a metric SE(2) trajectory with ten waypoints. To place motion in the same autoregressive interface as language and image-space points, we learn a residual vector quantizer over the Stage II trajectory distribution.
The tokenizer comprises three 256-entry codebooks. L0 selects a coarse trajectory; L1 and L2 encode successive residuals. The resulting three-token representation achieves a mean waypoint displacement error of 0.72 cm. Ablation supports three levels as the minimal sufficient hierarchy: two levels incur substantially higher reconstruction error, whereas additional levels or larger codebooks yield only marginal reductions. Every prefix remains decodable—L0 defines a complete coarse trajectory, and each subsequent token refines it.
Because the prediction interface and Stage II recipe remain unchanged, we can vary scale along three axes without changing the learning objective: the number of training environments, the number of aligned SFT examples, and model capacity. The analysis below asks which of these investments most reliably improves navigation.
Environment scaling has yet to saturate.
Across the range we tested, widening the set of environments is the most reliable way to improve the policy. All four measures rise at every step of environment scaling. Increasing model size produces mixed results, while additional SFT episodes from the same scene pool show diminishing returns. These results suggest that, at the current scale, adding new environments is likely to be more valuable than sampling existing ones more densely.
Real2Sim2Real makes that expansion practical. Each captured environment is reconstructed once, then reused to produce many aligned goals, routes, instructions, and camera views. More compute raises episode throughput; more scene assets broaden the visual and spatial variation those episodes cover.
Even broad SFT data has a boundary: it shows the policy how successful navigation unfolds, but not how to recover from its own mistakes. A late turn, an overshoot, or a lost target takes the policy into states that demonstrations rarely cover. Stage III keeps the same point-and-action interface but learns from a new source of experience—the policy’s own trajectories and their outcomes.
Train beyond demonstrations.
Stage III remains entirely in simulation. Instead of following routes supplied by the data engine, the model proposes complete plans and the simulator scores their outcomes. The policy’s own states—and its own mistakes—now shape the training signal.
GRPO11 learns from the relative outcomes of those plans. The action vocabulary stays fixed—RL operates on the same RVQ motion tokens introduced during SFT—while supervision shifts from imitating a successful route to improving the consequences of the policy’s own decisions.
The distracted-tracking split of EVT-Bench12 provides a consistent readout: performance rises beyond the SFT checkpoint before reaching a plateau (Fig. 11).
Tracking success during online RL
EVT-Bench Tracking DT, evaluated over 1,392 episodes in 101 scenes.
Across three stages, the model learns from broad spatial reasoning, aligned simulated interactions, and simulated outcomes from its own policy. The training loop ends here. What follows is transfer—across public benchmarks, physical embodiments, and unfamiliar visual domains.
Generalization across tasks, scenes, and embodiments.
Public benchmarks are the first transfer test. We evaluate the same checkpoint across ten settings spanning instruction following, object navigation, open-vocabulary search, and target tracking, using VLN-CE13, Matterport3D14 and HM3D10, HM3D-OVON15, and EVT-Bench12.
LightNav-0 uses a single egocentric RGB view, limited to the camera’s current field of view. Panoramic and multi-camera methods observe several directions at once. Each panel therefore shows two comparisons: monocular methods under the same sensing constraint, followed by results from broader-view systems.
LightNav-0 ranks first in all ten monocular comparisons. When broader sensing is included, it remains first in four (Fig. 12).
R2R
SR ↑ · 60–80All reported methods11 monocular · 17 broader-view
MONOCULAR
- LightNav-068.5MONO
- Qwen-RobotNav-4B66.9MONO
- Qwen-RobotNav-8B65.7MONO
- CorrectNav65.1MONO
- DualVLN64.3MONO
- InternVLA-N158.2MONO
- Qwen-VLA57.3MONO
- StreamVLN56.9MONO
- NaVILA54.0MONO
- Uni-NaVid47.0MONO
- NaVid37.0MONO
PANO / MULTI-CAMERA
- Qwen-RobotNav-8B72.1BROADER
- Qwen-RobotNav-4B69.5BROADER
- ABot-N168.3BROADER
- ABot-N066.4BROADER
- SPAN-Nav66.3BROADER
- NavForesee66.2BROADER
- NavFoM61.7BROADER
- HNR61.0BROADER
- ETPNav57.0BROADER
- Reborn50.0BROADER
- GridMM49.0BROADER
- DreamWalker49.0BROADER
- AO-Planner47.0BROADER
- Sim2Sim43.0BROADER
- CMA41.0BROADER
- HPN+DN36.0BROADER
- InstructNav31.0BROADER
RxR
SR ↑ · 60–80All reported methods10 monocular · 12 broader-view
MONOCULAR
- LightNav-073.6MONO
- Qwen-RobotNav-8B73.4MONO
- Qwen-RobotNav-4B71.3MONO
- CorrectNav69.3MONO
- DualVLN61.4MONO
- Qwen-VLA59.6MONO
- InternVLA-N153.5MONO
- StreamVLN52.9MONO
- NaVILA49.3MONO
- Uni-NaVid48.7MONO
PANO / MULTI-CAMERA
- Qwen-RobotNav-8B76.5BROADER
- Qwen-RobotNav-4B75.2BROADER
- ABot-N170.9BROADER
- SPAN-Nav69.7BROADER
- ABot-N069.3BROADER
- NavForesee66.3BROADER
- NavFoM64.4BROADER
- HNR56.3BROADER
- ETPNav54.7BROADER
- Reborn48.6BROADER
- CMA26.5BROADER
- Sim2Sim26.5BROADER
MP3D
SR ↑ · 40–60All reported methods5 monocular · 3 broader-view
MONOCULAR
- LightNav-053.3MONO
- CogNav46.6MONO
- SG-Nav40.2MONO
- OpenFMNav37.2MONO
- VLFM36.4MONO
PANO / MULTI-CAMERA
- Qwen-RobotNav-4B52.2BROADER
- Qwen-RobotNav-8B48.8BROADER
- WMNav45.4BROADER
HM3D v1
SR ↑ · 50–80All reported methods8 monocular · 1 broader-view
MONOCULAR
- LightNav-074.5MONO
- Uni-NaVid73.7MONO
- CogNav72.5MONO
- FiLM-Nav61.7MONO
- TriHelper56.5MONO
- SG-Nav54.0MONO
- VLFM52.5MONO
- OpenFMNav52.5MONO
PANO / MULTI-CAMERA
- WMNav58.1BROADER
HM3D v2
SR ↑ · 60–85All reported methods4 monocular · 2 broader-view
MONOCULAR
- LightNav-079.5MONO
- FiLM-Nav77.0MONO
- VLFM63.6MONO
- SG-Nav49.6MONO
PANO / MULTI-CAMERA
- Qwen-RobotNav-4B75.6BROADER
- Qwen-RobotNav-8B71.2BROADER
Seen
SR ↑ · 40–65All reported methods5 monocular · 4 broader-view
MONOCULAR
- LightNav-055.3MONO
- MTU3D55.0MONO
- Uni-NaVid41.3MONO
- DAgRL+OD38.5MONO
- VLFM35.2MONO
PANO / MULTI-CAMERA
- Qwen-RobotNav-4B57.7BROADER
- Qwen-RobotNav-8B56.1BROADER
- ABot-N055.3BROADER
- NavFoM37.7BROADER
Synonyms
SR ↑ · 40–65All reported methods5 monocular · 4 broader-view
MONOCULAR
- LightNav-053.3MONO
- MTU3D45.0MONO
- Uni-NaVid43.9MONO
- DAgRL+OD39.0MONO
- VLFM32.4MONO
PANO / MULTI-CAMERA
- Qwen-RobotNav-4B60.1BROADER
- Qwen-RobotNav-8B57.8BROADER
- ABot-N055.4BROADER
- NavFoM43.3BROADER
Unseen
SR ↑ · 35–60All reported methods5 monocular · 4 broader-view
MONOCULAR
- LightNav-047.0MONO
- MTU3D40.8MONO
- Uni-NaVid39.5MONO
- DAgRL+OD37.1MONO
- VLFM35.2MONO
PANO / MULTI-CAMERA
- ABot-N054.0BROADER
- Qwen-RobotNav-4B53.1BROADER
- Qwen-RobotNav-8B51.2BROADER
- NavFoM43.6BROADER
Single-target
SR ↑ · 85–95All reported methods5 monocular · 7 broader-view
MONOCULAR
- LightNav-091.7MONO
- ReferTrack89.4MONO
- VLingNav88.4MONO
- TrackVLA85.1MONO
- Uni-NaVid53.3MONO
PANO / MULTI-CAMERA
- CoMaTrack92.1BROADER
- ABot-N187.0BROADER
- ABot-N086.9BROADER
- TrackVLA++86.0BROADER
- NavFoM86.0BROADER
- Qwen-RobotNav-8B78.6BROADER
- Qwen-RobotNav-4B77.4BROADER
Distracted
SR ↑ · 65–85All reported methods5 monocular · 5 broader-view
MONOCULAR
- LightNav-082.6MONO
- ReferTrack73.3MONO
- VLingNav67.6MONO
- TrackVLA57.6MONO
- Uni-NaVid31.9MONO
PANO / MULTI-CAMERA
- CoMaTrack74.2BROADER
- ABot-N066.7BROADER
- TrackVLA++66.5BROADER
- ABot-N165.2BROADER
- NavFoM61.4BROADER
Rethinking navigation evaluation.
Most navigation benchmarks compress several abilities into one success rate. They are also concentrated in Habitat-style indoor scans and often use long route descriptions. When a model fails, the score does not reveal whether it misunderstood the goal, missed a spatial relation, or could not navigate the scene.
We built INSIGHT-Bench to separate those factors. It evaluates five atomic ways of specifying a goal—Base, Direction, Relation, Extremum, and Ordinal—across apartments, houses, commercial spaces, institutions, and outdoor environments. The benchmark contains 1,097 episodes in 210 held-out scenes. Among seven open-source policies evaluated under the same forward-RGB protocol, LightNav-0 achieves the highest success rate in every instruction and scene category.
BY INSTRUCTION
SUCCESS RATE · SHARED 0–70 SCALEBY SCENE
SUCCESS RATE · SHARED 0–70 SCALEZero-shot transfer is the test of embodied post-training.
A policy can be valuable on a single robot. Generalization is the stronger test: what remains when the body, environment, or task changes. LightNav-0 is evaluated along all three axes—across four physical robot embodiments, unseen indoor and outdoor environments, and three task families: long-form instruction following, open-vocabulary object navigation, and target tracking.
Beyond embodied navigation.
Scaling data matters only if the resulting policy works beyond the worlds that produced it. We therefore test the unchanged checkpoint far outside the visual distribution of its robot training data: first in closed-loop interactive worlds, then on open-loop in-the-wild video.
The two settings answer different questions. In interactive worlds, every predicted action changes the next observation, so errors accumulate and the policy is tested end to end. In video, the model cannot influence what it sees next. This isolates whether target grounding, free-space reasoning, and trajectory prediction survive unfamiliar cameras, motion, and visual styles.
Closed-loop control in unfamiliar worlds.
Each environment adds a different challenge. The voxel world changes scene geometry and texture. The driving world demands continuous steering at speed, leaving less time to correct drift. The first-person worlds introduce legacy graphics, and the final one also changes both resolution and aspect ratio with a lower-resolution 4:3 frame.
Open-loop visual transfer.
Mountain biking, speed skating, freestyle skiing, and trail running introduce rapid egomotion, occlusion, scale change, and non-robot camera dynamics absent from the embodied post-training data. Across these videos, LightNav-0 continues to ground the target and predict feasible motion frame by frame.
LightNav-0 is open.
The release brings together the model, code, and technical report behind LightNav-0. A broader evaluation suite will follow.
We thank our collaborators at LimX Dynamics and Manycore Tech for their support across physical deployment and simulation.