The
robot capability is in beta — see the Robots reference.The environment
The env module is declare-only — a sim bridge, an endpoint, and two-yield templates (this isdemos/benchmarks/envs/libero/env.py, abbreviated):
env.py
hud serve env.py --host 0.0.0.0 --port 8765); build once from the repo root:
The agent
A stock LeRobot checkpoint needs no custom Model or Adapter:run_libero.py
Run it
DockerRuntime is the placement: each rollout docker runs a fresh container, publishes the control port, connects, and removes the container afterward. The agent reads the env’s contract from the manifest at connect time and wires cameras/state/actions itself — there is no shared config between this script and the image. The robot WebSocket binds container-loopback and rides the control port via capability tunneling.
For heavy sims (or sweeps), skip the per-episode boot with one long-lived container:
Read the trace
WithHUD_API_KEY set, every episode streams to the platform automatically: the trace viewer plays the camera frames back under a scrubber, with diamond markers at each step where the policy predicted a fresh action chunk — scrub between markers to watch a chunk execute, click one to jump to the decision point.
See also
Robots reference
Contracts, bridges, realtime control, and the harness API.