Skip to main content
Version: v5.6.1

opschain runs artifacts

Included from Basic tier

opschain runs artifacts <run-id> [--download <name>] [--out <dir>]

Lists a run's stored artifacts newest-first — the step artifacts collected at step completion (opschain docs artifacts) plus any the action stored through the artifact DSL — or downloads one by name. Works on the local lane (--local) and against a server.

On the local lane a workflow run's listing includes, recursively, the artifacts of every change its workflow steps spawned. Against a server the run id must be a change's — a workflow run's artifacts live on the changes it spawned, which opschain runs show <run-id> -o json names as each step's nested_run_id.

Flags​

FlagMeaning
--download <name>Fetch the run's newest artifact stored under this name instead of listing. A collected step artifact (content type application/x-tar) is unpacked under --out with its workspace-relative paths; any other artifact is written to --out as a single file named after the artifact.
--out <dir>Where a --download lands (created if missing). Default: the current directory.

Output​

NAME FILES SIZE TYPE CREATED BY

A purged artifact (retention tombstoned it) shows (purged) after its name and refuses download with the purge named. FILES is - for artifacts stored as raw content. -o json|yaml prints the summaries structured.

Exit codes​

CodeMeaning
0Listed, or the download landed.
1The read failed — unknown run or artifact name, a purged artifact, or a server error.
2Usage error.

See also​

  • opschain docs artifacts — declaring step artifacts, budgets, retention and the masker caveat.
  • opschain docs cli/artifacts-list / cli/artifacts-get — the node-scoped artifact surface.
  • opschain docs cli/runs-show — naming a workflow run's spawned changes.