Tesla Optimus, Figure's humanoids and 1X NEO run proprietary policies on proprietary software stacks. Their makers publish demonstrations, but not a robot interface, joint/action specification, SDK or configuration that an outside policy can be trained against or deployed through. A compatibility cell for “SmolVLA on Optimus” could only ever be a guess, and this reference does not publish guesses.
Adding empty rows would make the grid look larger and less honest. They get this page instead.
What would change it
- A public SDK or robot interface that accepts external policies (as Unitree G1 and Reachy 2 have through LeRobot).
- A public dataset recorded on the robot in an open format such as LeRobotDataset.
- An upstream statement, model card or paper documenting a named open policy running on it.
If any of these appears, open an issue with the link and the robot gets a row.