Retrieve job outputs

simulo outputs shows everything a job produced in one list: its checkpoints, its MCAP recordings, an export’s ONNX bundle, and files the job saved with simulo.save_output. Use it to see what a job made, then download what you need.

1. List what the job produced

With no job ID, the command uses your most recent job you submitted (train, play, preview or eval). Export jobs are skipped, so it does not select the export job a simulo export you just ran created:

simulo outputs

Name a job to pick a specific one:

simulo outputs <job-id>

The table has these columns: KIND, NAME, SIZE, CONTENT TYPE, CREATED and OUTPUT ID. Common kinds:

Kind	What it is	Name	Output ID
model_checkpoint	A training checkpoint	best.pt or latest.pt	The checkpoint reference, such as policy_brisk-heron-4f8k2m:best
recording	An MCAP recording a play job made	The recording’s file name	An ID starting with rec_
anomaly_capture	An MCAP recording from anomaly capture	The recording’s file name	An ID starting with rec_
onnx_bundle	The ONNX bundle an export job made	{job name}-policy-{kind}.zip	An ID starting with out_
file, report, dataset and others	A file the job saved with simulo.save_output	The name the job gave it	An ID starting with out_

The table shows 20 items by default. Use --limit N for 1 through 250 items, or use JSON without a limit when you need the complete machine-readable list:

simulo outputs <job-id> --limit 100
simulo outputs <job-id> --json

2. Download one item

Pass a name or Output ID from the list, and choose where to save it:

simulo outputs <job-id> best.pt -o ./best.pt
simulo outputs <job-id> recording.mcap -o ./recording.mcap

Replace recording.mcap with a name from the NAME column. If two outputs share a name, the command refuses and lists their Output IDs, so pass the ID instead. When -o names an existing folder, or ends with /, the file keeps its own name inside that folder.

The CLI checks the downloaded bytes against the recorded digest when one is available. A mismatch fails the command instead of leaving a file you might trust by mistake.

3. Download everything

simulo outputs <job-id> --all -o ./job-outputs/

--all downloads every output; it does not expand the table. The -o value is a directory for this form.

When you already know the kind you want, the dedicated commands are shorter: simulo policy get policy_brisk-heron-4f8k2m:best for a checkpoint, and simulo recordings <job-id> for MCAP recordings.

Save a file from a job

Call simulo.save_output(name, path) from a job body to register a produced file. Returning from the job successfully makes eligible registrations available to the worker for upload. A file appears in simulo outputs alongside recordings only after that upload is persisted. Checkpoints appear in simulo outputs too, as the model_checkpoint kind; simulo policy get is the dedicated way to download one.

name is one plain file name, never a path, and path is where the job wrote the file. An optional kind, such as "report" or "dataset", describes the file and defaults to "file". A job can register up to 1000 files.

A cancelled, timed-out, crashed, or failed job does not deliver files it registered this way, and a refused or unsuccessful upload can also leave a registration undelivered. Return normally after writing the file, then confirm it appears in simulo outputs.

Download from Simulo Console

Open Simulo Console, choose Jobs, select the job, then open its Outputs panel. It lists the same outputs, each with a download action and a button to copy its Output ID.