Artifacts
Files an agent exports from its sandbox, where they are kept, and how to download them with a short-lived link and check them.
An artifact is a file an agent exports from its sandbox with the export_file tool: a report, a patch, a dataset. Each export adds an artifact.created event ({artifact_id, name, size}) to the task's stream.
Where artifacts are kept
Artifacts are stored in your organization's storage, next to the runtime that ran the task. In the private preview, that is a storage account Hexel Studio hosts for your organization alone. The harness's control plane keeps each artifact's id, size and a digest of its name, not its bytes.
Once a task has succeeded, an artifact's name is emptied in the control plane (its name_digest stays), like the task's goal; the file itself keeps its name in storage.
Download an artifact
hexel harness artifacts list tsk_123
hexel harness artifacts pull tsk_123 # every file, into the current directory
hexel harness artifacts pull tsk_123 art_1 --dir out # one file; --force overwritesThrough the API, GET /harness/tasks/{id}/artifacts/{artifact}/download returns a short-lived link straight to the file in storage:
{
"method": "GET",
"url": "https://...",
"headers": {},
"expires_at": "2026-11-17T10:15:00Z",
"content_sha256": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
}Fetch url with method and headers, then check the bytes against content_sha256. The bytes never pass through the harness. The CLI checks the SHA-256 before it saves a file, and keeps an existing file unless you pass --force.
| Error | Meaning |
|---|---|
409 not_downloadable | The artifact has no copy in your storage. |
502 download_failed | The runtime could not make a link for it. |
504 cell_unavailable | The runtime that holds it did not answer within 20 seconds. A parked task's artifacts can be downloaded once it resumes. |
429 too_many_downloads | More than 20 downloads are waiting in your organization. Try again shortly. |
Reading artifacts needs harness:artifact:read: Members and Viewers can read their own tasks' artifacts.
Deleting tasks
Deleting a task, or its removal at the end of the retention period, does not delete its artifacts: they stay in your storage. See Data retention.