AI JobsStart a program

AuraOne / Resources / AuraOne Open

Robotics Studio Open

Robotics Studio Open 0.2.0 is a local-first desktop release under the MIT license for reviewing supported teleoperation and VLA datasets. Adapter compatibility, optional probes, and export destinations depend on the release and local configuration.

All articles
Robotics Studio Open cockpit showing an open LeRobot dataset, episode count, and the review workspace
Published
2026-05-14
Reviewed
2026-07-17
Author
AuraOne Open team
Category
AuraOne Open
Reading
2 min

At a glance

Article details

Editorial
Sources
2 structured source records are attached to this article. Recheck external material at the time of use.
Scope
This is dated analysis. Product availability, model behavior, and regulatory requirements may all change after publication.
Format
AuraOne editorial analysis

Every serious robotics team has a private dataset review tool.

It might be a Streamlit app. It might be a notebook. It might be a custom desktop wrapper around a folder of videos and parquet files. The shape is always similar: list episodes, play videos next to joint state, mark success or failure, write a few tags, export the subset that training should see next.

The workflow is standard. The tooling is not.

Robotics Studio Open is now at 0.2.0, a local-first macOS Apple Silicon release and an IDE for reviewed teleoperation and VLA datasets. The release notes report Developer ID signing and notarization. Supported formats and synchronized streams depend on the adapters and optional dependencies in the release; this overview does not guarantee compatibility with every LeRobot, RLDS, Open X-Embodiment, HDF5, ROS bag, or custom capture.

The repository includes review, clustering, robustness, embodiment-card, and export workflows. Users should verify each workflow against their dataset and the current release documentation.

The integrated robotics OSS surface

Robotics Studio Open brings six AuraOne robotics projects into one daily surface:

  • lerobot-quality-gates for dataset health checks
  • robot-recovery-bench for intervention and recovery metrics
  • vla-robustness-kit for perturbation probes
  • embodiment-card for robot and dataset cards
  • robotics-reviewkit for review schemas and taxonomy
  • failure-gallery for shareable failure cases

The standalone CLIs remain. The studio is the product surface for daily review.

Local first by design

Robot datasets are large, private, and operationally sensitive. Robotics Studio Open is not a hosted browser editor. It is a local-first desktop app and CLI. The sidecar index, thumbnails, review tags, sensor anomaly notes, and saved views stay with the dataset unless the user explicitly exports them.

That local-first boundary also keeps the commercial line clean. Robotics Studio Open is single-user and MIT licensed. Multi-reviewer queues, hosted dataset storage, approval chains, audit ledgers, RBAC, SSO, and managed reviewer pools belong to Robotics Studio Cloud, Robotics Studio Enterprise, and AuraOne Robotics Programs.

What the first workflow looks like

Open a dataset. Browse episodes without loading every video into memory. Scrub the synchronized streams. Tag a failure. Cluster similar failures. Run sensor QA. Generate an embodiment card. Export a reviewed subset to Hugging Face or create a privacy-reviewed AuraOne Programs intake export.

That is the loop robotics teams keep rebuilding internally.

Now it has a public surface.

Review the Robotics Studio Open v0.2.0 release, see the read-only example build at robotics-studio.auraone.ai, or start from the product page at Robotics Studio Open.