Drag back the time bar. See what happened.
A run is a folder of streams: the frames the engine made, and every command, recorded before it was sent. Replay reads those files; it does not run anything again.
One recorded run
One minute of an arm, five files.
On 2026-11-03, scripts/sim/robot-runs.mjs recorded 160 runs of the so101-cube world, each with drags of the cube at random moments. This is the first run's folder as stored in CommandAGI's Drive, with its sizes, then its first drag as recorded. Replay reads these files and nothing else.
run.json 389 B reality=simulation streams/sim@robot-0/stream.json 2,626 B sim-state, 92 f64 fields streams/sim@robot-0/data.bin 1,325,536 B 1,801 frames, 60 s at 30 Hz streams/sim-input@robot-0/stream.json 208 B streams/sim-input@robot-0/records.jsonl 1,359,920 B 1,798 records 05:56:49.352 command agent:robot-trajectories: grab cube target=[0.141,-0.040,0.822]
Who sent what
Every command names the principal that sent it.
The run holds 899 commands, each recorded before the engine applied it, and 899 engine events, each naming the step its command took effect at. A replay shows each command at its moment on the time bar, beside the frames it changed.
- commands by
agent:policy-mover, the arm's policy - 881
- by
agent:robot-trajectories: 9 grabs, 9 releases - 18
- of wall time recorded the 60 simulated seconds
- 3.05 s
- such runs in the Drive: 800 files, 428 MB
- 160
Simulated
cloud://home/user-commandagi/simulations/so101-cube/drags/runs/20261103t055648z-04x4/streams/sim-input@robot-0/records.jsonlOutput case-studies/replay/stats.jsonTool scripts/sites/case-studies.mjs replayRan on This computer (dell-gb10-1), reading the production DriveWhen Every run plays back.
A physical run records the same way, with the device's own replies. A lost link is recorded as a state that is unknown, never guessed.