Teleop server.

When to use it

• You want a safety reviewer to watch a session live and flag issues before a clip lands.
• You're running Tier 4 operators on a full teleop cell and want the session stream routable across sites.
• You want a shared backchannel between operator, coach, and safety reviewer without building it yourself.

When not to use it

• You already run a teleop platform (your own or a vendor's) and just want to feed reviewed clips into the lab. Use the SDK.
• You're capturing on iPhone only. The capture app handles chunked resumable upload on its own.

Session lifecycle

// 1. Create a session
POST /v1/robotics/sessions
{
  "task_brief_id": "tb_01J...",
  "operator_id": "op_01J...",
  "tier": 4
}

// 2. Server returns a LiveKit room token
{
  "session_id": "sess_01J...",
  "room_url": "wss://...",
  "token": "ey..."
}

// 3. Operator cell connects; reviewer joins as observer
// 4. On end, clips emit to the scoring pipeline
// 5. Approved clips land in the customer tenant; rejected clips land in the regression bank

Native I/O

The teleop server speaks MCAP and ROSbag natively. Both directions. You can mirror a session into your existing telemetry pipeline while the lab scores it in parallel.