AI

Hydra-0 Treats Robot Actions as Pixel Motion

Robb Harlan 5 min read

A team from NVIDIA, Brown, Columbia, and Harvard posted Hydra-0 on Aug. 18: a world model that conditions on action flow, meaning robot actions as pixel motion in the camera plane instead of joint commands.

Their best setup reports 90.4% lower robot-motion error and 60.2% lower object-motion error than an action-conditioned Cosmos 2.5 baseline. On the RoboLab benchmark, replayed versus reference success rates hit Pearson r = 0.96.

Cloth-folding comparison of Wan-Move, Cosmos 2.5, Hydra-0 action flow, and ground truth
Five-second XVLA-Soft-Fold rollouts. Action-flow conditioning tracks the commanded fold better than the native-action baseline. Source: Li et al., arXiv:2608.18077.

Why pixel tracks instead of joints

Joint commands encode one robot’s kinematics. The same end-effector command can look different on another arm. Hydra-0 maps a candidate command through the controller and physics in Isaac Lab, then projects visible robot-surface points into the image. The video model sees where the robot should move on screen.

At training time they recover the same tracks from videos when calibration is missing: dense flow plus grounded masks. The training corpus is 2,201.7 hours after filtering, spanning DROID, ABC-130k, MolmoAct2, EgoDex, Deform360, and smaller cloth-fold sets, including a Unitree H1 fold-clothes slice.

They plug the same interface into Cosmos 2.5 and Wan2.2. A four-step distilled Wan2.2 A14B checkpoint is the strongest row in their table. Few-step distillation reaches 62.0 frames per second generation-only on one H100, a 16.0× speedup versus the bidirectional teacher, excluding VAE decode.

Hydra-0 training and deployment diagram with video-derived and camera-projected action flow
Offline: recover flow from video. Online: project an Isaac Lab command into the camera and predict the consequence. Source: Li et al., arXiv:2608.18077.

Inverse mode: object flow in, robot motion out

Flip the interface and the model becomes a world action model. Give it desired object flow from a human demo, withhold gripper flow, and a trained head maps latents to executable actions. They show a flexible-pipe-bending task on a real bimanual setup. No task-specific expert robot demonstrations, they say. The paper also notes roughly 1 cm of grasp imprecision as a limitation.

Open-loop policy evaluation covers five RoboLab policies over six tasks (300 episodes). Generated success tracks the reference ranking. A real-world cloth-folding replay is a qualitative check, not a full closed-loop study.

Successful and failed cloth-folding rollouts, reference versus Hydra-0 prediction
Open-loop replay of a success and a failure. Source: Li et al., arXiv:2608.18077.

A Human’s Take

Conditioning a video model on “where the metal actually goes in the picture” is the kind of interface I can inspect. The Cosmos ablation is the useful bit: swap 6D actions for pixel tracks on the same backbone and the error drops.

RoboLab correlation of 0.96 is open-loop replay, not a robot choosing its next move from a dream. Fine. If you want a world model that transfers across arms and hands, start by refusing to hide the kinematics in a joint vector the pixels never see.

Sources