Skip to main content
Artifacts are files or directories collected from the sandbox after the agent runs. Declare them in task.toml to preserve outputs for inspection and transfer them to a separate verifier.

​
Configuration

Set artifacts at the top level of task.toml, before any section headers:
task.toml
Harbor saves these under <trial-dir>/artifacts/app/. View them in the results viewer’s Artifacts tab.

​
Advanced options

Use an object to customize collection. Strings and objects can be mixed:
task.toml
For sidecar outputs and pre-collection commands, see Sidecar artifacts.

​
Separate verifiers

A separate verifier starts in a fresh sandbox, without the agent’s filesystem changes. Declare every agent-produced file it needs as an artifact. Harbor collects these after the agent runs and copies them into the verifier before grading.
task.toml
The verifier can read the report at /app/report.json. Artifact paths are preserved; destination only changes the saved path on the host. No separate transfer configuration is needed. Undeclared outputs are not transferred, except for the currently automatic /logs/artifacts/ directory. Dedicated verifier images bundle grading code; when reusing the agent environment, Harbor uploads tests/. See Image selection.

​
Multi-step tasks

Add step-specific outputs under [[steps]]:
task.toml
These are added to task- and run-level artifacts, collected before the step’s verifier, and saved under steps/<step-name>/artifacts/. See Multi-step.
Automatic collection from /logs/artifacts/ will be removed soon. Declare artifacts explicitly for new tasks.
For CLI/run-level additions and collection reports, see Artifact collection.