Skip to main content
Upload results from another machine or runner. Evolve imports their trials, rewards, and traces as a completed job.
This example links results for DeepSWE tasks to deepswe@1.1. Replace the dataset with the version used for your run. The source must use the supported job layout; a local directory needs config.json and result.json at its root. For an SDK session log, use the packaging walkthrough first.

Choose a source

Use one source per invocation. --from requires a public HTTPS URL.

Options

Dataset linking makes the stored task available to later analysis. Review the report for unlinked tasks and skipped trial folders.

Follow an import

By default, upload waits for the imported job. Use --no-wait to return after the upload is accepted:
Copy the complete import ID from that output into $IMPORT_ID, then follow it:
With --json, the default command prints one final job document. With --no-wait --json, it prints the import record instead. A failed import returns exit code 1 when watched. Exit code 0 with --no-wait confirms acceptance; the import can still fail later.

Inspect the result

Use the imported job’s ID from the completed upload or job import output as $JOB_ID:
Uploaded costs are reported by the source archive, not metered execution on Evolve. Uploaded jobs can be analyzed, but cannot be resumed, retried, or regraded. Global options apply.
Last modified on November 9, 2026