Artifacts

Artifacts are files captured under the run state directory for later inspection. They are useful when a substep produces command output, diagnostics or structured result data that should be kept separate from the SQLite checkpoint database.

Declare artifacts on a substep:

- id: collect_version
  use: command.remote.run
  with:
    command: "myapp --version"
  artifacts:
    stdout: version.txt
    stderr: version.err

Supported artifact sources are:

• stdout: plugin standard output.
• stderr: plugin standard error.
• data: plugin structured result data as JSON.

Artifact names are relative paths below the node artifact directory. Absolute paths and .. path traversal are rejected.

automax artifacts list <run-id>
automax artifacts path <run-id>

For handover or audit evidence, use the run evidence commands. runs export writes a Markdown or JSON report, while runs bundle creates a ZIP containing the reports, an artifact manifest and captured artifact files:

automax runs export <run-id> --output evidence.md
automax runs bundle <run-id> --output automax-evidence.zip

Example visual layout:

.automax/runs/20260523-demo/artifacts/
  web01/
    task.deploy_step.check_substep.version/
      version.txt
      version.err

Secret values resolved by Automax are masked before artifact content is written.