When to use it
Use it after a teleoperation session is captured.
Robotics Studio Open does not include a hosted teleoperation server. Use your existing capture system, then export the session context and local file references into a supported JSON or JSONL manifest.
Session
session metadata
Keep the task, operator, device, timing, and environment context together.
Media
local paths
Reference local video, depth, state, action, and sensor files without uploading them.
Roles
operator + reviewer
Preserve operator, coach, observer, and reviewer roles in the session metadata.
Rights
consent + license
Carry consent, license, and safety context into the review manifest.
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.
{
"format": "auraone-robotics-manifest-v1",
"session_id": "sess_01J...",
"task_brief_id": "tb_01J...",
"operator_id": "op_01J...",
"device": { "model": "so101", "control_rate_hz": 30 },
"streams": {
"rgb": "./sessions/sess_01J/rgb.mp4",
"state": "./sessions/sess_01J/state.jsonl",
"action": "./sessions/sess_01J/action.jsonl"
},
"consent_receipt": "consent_01J...",
"license_scope": "lic_01J..."
}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.