Hugging FaceSundar Raghavan, Cagatay CaliTutorial
From the Hugging Face Hub to robot hardware with Strands Agents and LeRobot
Summary
Strands Robots integrates Hugging Face’s LeRobot stack with Strands Agents to connect dataset recording, policy execution, simulation, hardware deployment, and fleet coordination in one agent loop. Its integration keeps LeRobot responsible for hardware drivers, calibration, recording, and dataset handling, while Strands supplies AgentTools, a shared Robot abstraction, policy providers, and a Zenoh peer mesh; simulation and hardware use the same LeRobotDataset format. The walkthrough records demonstrations in MuJoCo, optionally pushes them to the Hub, runs policies through a common interface, and switches from simulation to a physical SO-101 with mode="real". The companion script and notebook run the default simulation workflow on a laptop without hardware, a GPU, or Hugging Face credentials, although the default Mock policy produces structurally valid but behaviorally unhelpful random demonstrations.
Context
The workflow addresses a robotics setup in which recording demonstrations, training, simulation testing, hardware deployment, and multi-robot coordination use separate tools that do not interoperate. It also provides a path to test the workflow without hardware or a GPU, while preserving compatibility between simulation and hardware datasets.
Approach / What changed
Strands Robots exposes LeRobot capabilities as AgentTools composed into a single Strands agent. LeRobot continues to handle hardware recording, calibration, drivers, and dataset storage; Strands adds the orchestration layer, shared Robot abstraction, policy interface, and Zenoh peer mesh. Simulation and hardware write or consume the same LeRobotDataset format, and switching to a physical SO-101 uses mode="real".
Takeaways
The simulation recorder uses the same LeRobotDataset structure as hardware recording, including parquet data for joint states and actions and per-camera MP4 files.
The Mock policy generates placeholder random joint actions, producing a structurally valid dataset but not a useful grasping demonstration; GR00T or LerobotLocal can be substituted for real policy behavior.
The default example runs on a laptop without hardware, a GPU, or Hugging Face credentials, while local GR00T inference requires an NVIDIA GPU with at least 16 GB of video memory and Docker.
Source and freshness
- Source
- huggingface.co
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.