Record, train, and deploy from one place with Strands Agents, LeRobot, and Hugging Face Storage Buckets
- ID
- 13905
- Status
- summarized
- Published
- 14 Aug 2026, 1:16 AM
- Fetched
- 14 Aug 2026, 1:43 AM
- Provider
- Hugging Face Blog
- Category
- developer-ai
- Original URL
- https://huggingface.co/blog/amazon/strands-lerobot-streaming-data-loop
- Source URL
- https://huggingface.co/blog/feed.xml
Summary
- Score
- 4.5
- Created
- 14 Aug 2026, 1:43 AM
- Tags
- Audience
- developersai_ml_learners
What happened
AWS authors walk through a continuous data loop using Strands Robots (Apache 2.0 SDK), LeRobot's on-disk dataset format (90,000+ datasets, 8,000+ publishers on HF Hub), and Hugging Face Storage Buckets (mutable, non-versioned, Xet-backed object storage announced March 2026) to record robot demonstrations, train policies on growing datasets, and deploy back to hardware like the SO-100/SO-101 arms. The core problem they address is that running this loop daily causes repeated full-dataset transfers to GPUs and redundant byte costs, which the Storage Bucket layer sitting in the hf:// namespace is meant to mitigate as a working staging layer between recording and training.
Why it matters
If you are building robotics learning pipelines with LeRobot-compatible datasets, HF Storage Buckets give you a mutable staging layer that avoids re-copying the entire dataset to GPUs on every training run—a concrete cost and workflow decision. For everyone else, this is a niche robotics tooling walkthrough that doesn't require any change to what you ship.
Discussion angle
Whether HF Storage Buckets' mutable, non-versioned model is a useful pattern beyond robotics—for staging large training datasets between collection and GPU training runs without paying full transfer costs each iteration.