When to use it
Use it after a teleoperation session is captured.
Robotics Studio Open does not include a hosted teleoperation server. Connect your existing teleoperation capture system by exporting the session context and local file references into a supported JSON or JSONL manifest.
Session
session metadata
Keep the task, the operator, and the environment context together.
Media
local paths
Reference local video, depth, and action files. Nothing is uploaded.
Review
review state
Each episode carries reviewed, unreviewed, or unknown.
Rights
your system
Reference consent, license, and operator records from your primary capture system.
Manifest
Describe the session for local review.
Export a manifest from your capture system with local media references and the context Robotics Studio needs to review clips.
{
"schema": "auraone.robotics.dataset-manifest.v1",
"name": "teleop_session_0142",
"format": "JSON manifest",
"episodes": [
{
"id": "teleop-0142-ep-01",
"task": "open_drawer",
"embodiment": "SO-101",
"duration_s": 18.2,
"frame_rate_hz": 30,
"success": "success",
"reviewed": "unreviewed",
"sensors": [
{ "id": "cam-front", "kind": "rgb", "rate_hz": 30 },
{ "id": "joints", "kind": "joint", "rate_hz": 120 }
],
"interventions": [
{ "start_s": 9.4, "end_s": 11.0, "why": "operator takeover" }
]
}
]
}Review
Open the manifest and review locally.
Load the manifest in Robotics Studio, inspect synchronized streams, mark failures and recoveries, run quality checks, and export the reviewed subset as a local archive.