The sweep stays with your simulator
mutational stale runs your adapter, in CI or on a workstation. Add --record-runs runs.jsonl and every run is kept. Commands that need a simulator are refused here, with a sentence saying why.
The real binary, in this tab
Compiled to WebAssembly and otherwise unchanged, with a real recording beside it: six Meta-World manipulation tasks swept in MuJoCo, 542 simulator runs. Replaying it takes well under a second, and the page says how long.
Loading the binary…
Pick something from the list, or type a command. `mutational -h` lists them.
Files in this tab
Commands read and write these by name. They live in this tab's memory and nowhere else: closing the tab is deleting them.
Drop your own files here, or click to choose - a recording (
--record-runs), a suite, a history (--record), facts, a catalogue. They are read where they are. Nothing is uploaded: the account API on this site refuses anything over four kilobytes.Analyse your own files - free.Sign in with your email to drop in your own recordings. The demo and the sample above need no account.
Sign inReading happens anywhere. Sweeping happens where your simulator is.
The report is the binary's own
A recording replays into the full report with the settings it was made with - the same text the command line prints, not a rendering of it. Ask for other settings and it says how many runs are missing.
Nothing you open leaves the tab
The binary runs in a worker that refuses every file until it has deleted its own fetch - the only way a Go binary in a browser reaches a network. This site's headers refuse the worker any connection but to this site's own static files.