(01)“For robotics researchers”

Early accessSept 2026

Collect sim teleop data with a shareable link.

Human demonstrations in simulation · pilots need a VR headset and wifi · Quest Browser on supported devices

01 / 05

(02)“Founding research partners”

Early accessSept 2026

02For robotics researchers

Your sim,playablein VR.

Share one link. Pilots just need a VR headset and wifi.

No installNo accountQuest Browser

MuJoColift.pyYour sim
robosuite's Lift task running in MuJoCo's viewer on your machine.
$ herbie sim publish

herbie / play / lift-the-cubeShare link

“Pilot” · @kay Successep_0142 · saved to successes
Rec · ep_0142 @kay · Quest 3
  • Grasp the cube
  • Lift it clear
  • Hold it at the goal

Lift the cube

Play in VR 3 playing now

Human demonstrations in simulation · Quest Browser on supported devices · prototype demonstrated Sept 2026, hosted release planned · play page illustrative · logos belong to their owners

02 / 05

(03)“How it works”

First release · robosuite on MuJoCoScreens illustrative

03From your laptop to their headset

Bring your sim.Publish it.Share the link.

  1. robosuite on MuJoCo first. Our SDK adds VR controls; your physics and task rules stay yours.

  2. One command uploads it. We build, check and host it in the cloud.

  3. Try it in your own headset, then publish it privately.

  4. Pilots just need a VR headset and wifi. It opens in Quest Browser: no install, no account.

+ VR grab target sample recording · automatic “Preview” · you “Pilot” · @kay Successep_0142 · saved to successes
Terminal · your machineSDK

$ herbie sim init --entry my_project.env:make_env

✓found Lift · Panda · robosuite on MuJoCo

herbie.toml[exports.lift]entry = "my_project.env:make_env"profile = "robosuite-arm-v1"
viewer · lift.pyYour sim
robosuite's Lift task running in MuJoCo's viewer on your machine.

+ VR controlsadded by the SDK

  • Hand posemoves the gripper · OSC
  • Triggercloses the gripper
  • Menustart and reset the task

$ herbie sim prepare

  • ✓uploadedlift_panda/ · 38.4 MB
  • ✓builtuv.lock · in the cloud
  • ✓controlshand → gripper
  • ✓visualsheadset scene
  • ✓recordingsample episode · saved
Sample recording · automatic00:00.00
  1. startclean reset
  2. graspcube held
  3. liftcube +0.18 m
  4. successtask reports success

Hostedlift_panda v3

  • Cloud runtimebuilt from your repo
  • One machine per sessionisolated, started on join
  • Episodes storedchecked · replayable

Ready to preview

Preview · your own headsetPrivate

✓Tried in your headsetcontrols · visuals · reset

$ herbie sim publish

PublishPublished · unlisted
Preview · you Quest 3
  • Controls feel right
  • Task resets cleanly
  • Visuals look right

Release v3your limits

Visibility
Unlisted · link only
Sessions
1 per pilot
Expiry
24 h
Spend
Capped

Revoke any time

Rec · ep_0142 @kay · Quest 3
  • Grasp the cube
  • Lift it clear
  • Hold it at the goal

Episodescoming in

  • Successep_0142@kay
  • Successep_0143@mo
  • Failureep_0144@lin

Sorted · replay · download

Quest Browser on supported devices · commands from the first-release CLI · screens illustrative · MuJoCo, robosuite, WebXR and Meta Quest belong to their owners

03 / 05

(04)“We collect and classify”

First release · robosuite on MuJoCoExamples

04We auto-collect and classify

Every attempt, recorded.Sorted by your own check.

Every attempt is saved in full and sorted into successes and failures by your task's own success check. Replay any episode, or download the dataset.

PlannedLeRobot exportRendered camera viewsMore robot types

@kayQuest 3 · LiftRec @moQuest 3S · LiftRec @linQuest 3 · LiftRec 01“Recorded in full”every attempt · automatic 02“Sorted by your check”your task's own success check 03“Replay”in the browser · any time 04“Download”the full native episodes pilot commands applied actions full sim state events + outcome 138successes 32failures ep_0218

In every episodeprovenancestart statepilot commandsapplied actionsfull sim stateevents + outcome

DemonstratedSept 2026 prototype: a human Quest pilot completed Lift and Can; records passed checks; replay ran after the runner stopped. Pipeline feasibility, not learned performance.

One episode = one recorded attempt, from simulation · practice is never recorded · the outcome comes from your task's check, never from herbie · pilots, ids and counts are examples

04 / 05

(05)“Your task”

Early access

05Early access · let's talk

Got a sim thatneeds teleop data?

We're opening early access to a few research teams. Tell us your task.

Tell us your task

No commitment. Just a conversation.

Join the waitlistearly access · two minutes Read the docshow it works, in depth

“Your teleop data”