Skip to main content
A dataset version is a named collection of tasks. Jobs select name@version, or the active version when only the name is given.

Browse the catalog

The detail view includes versions, tasks, build failures, and provider information.

Check before publishing

This reads local task metadata and sends it to Evolve for validation. It does not publish the corpus or run the tasks. The report includes a Harbor: line naming the supported task-format versions. When accepted tasks use newer fields, it also names the oldest release they require. A Terminal-Bench 1 task (task.yaml, no task.toml) fails the check and names harbor tasks migrate. The command returns exit code 1 if any task or the dataset manifest is refused. With --json, it prints one report containing tasks_refused and the manifest result. For an agent-based quality check, use evolve check.

Publish a version

Choose one source.
A dataset.toml manifest can supply the name and version. Local publishing runs metadata preflight before uploading.

Publish options

Do not combine source types. For a local directory, refused metadata stops publication before upload. --skip-preflight skips that early check; import validation still applies.

Follow the build

A READY version can contain failed tasks. The final report shows how many built and which failed. On your own dataset, the new ready version becomes active. To reconnect while an import is running:
To inspect a specific import, including one that has already finished, set $IMPORT_ID to the full ID printed during publishing:
Watching by dataset name selects an active import; when none exists, the command returns nothing_to_watch and exit code 1. With --json, publication without --watch returns one import record. Watching prints one JSON record per line, ending with import.final. A failed import or a build that cannot be confirmed returns exit code 1; a READY version with some failed tasks returns 0. Use a new version label for changed tasks. Publishing an existing label replaces its contents, so name@version does not guarantee unchanged content. If watching returns import_not_found because the upload was abandoned or refused before it arrived, repeat the publish command.

Change the active version

The chosen version must be READY. This changes what a bare my-benchmark selects; version-pinned jobs still use their selected version.

Download the corpus

-o, --output-dir <dir> sets the destination; the default is the current directory. This downloads the original stored corpus package. Access is limited to the dataset owner.

Read one task’s files

Use dataset files status/list/cat for package metadata, folder pagination, and byte ranges. These commands require an explicit dataset version. Global options apply. Next, run a job against the published version.
Last modified on November 9, 2026