Run

An artifact is a durable file produced by a loop or agent. Reports, images, audio, PDFs, generated source, and structured exports can all become artifacts.

Artifacts are the publish boundary for work done in an environment. The environment is where files are created and changed. An artifact is the output you want to keep, inspect, download, or reuse after that workspace is gone.

When to create an artifact

Create an artifact when the output should:

• Appear on a run timeline.
• Survive environment cleanup.
• Be downloaded or previewed by a person.
• Carry a checksum and trustworthy run lineage.
• Be passed to another system as a durable file.

Do not treat an environment file as the only copy of a deliverable. Publish the important output before the run finishes.

Browse artifacts in the app

Open Runtime > Artifacts to see files across the project. The list shows each artifact's name, type, size, and creation time. Search by name or filter by file type when the project has many outputs.

Open an artifact to preview supported text, markdown, JSON, image, audio, PDF, or self-contained HTML content. Large or unsupported files show a download action instead of loading the full file in the browser.

The detail page also shows:

• The run and step that produced the file, when present.
• Visibility and ownership.
• File size, media type, and creation time.
• Artifact ID and SHA-256 checksum for verification.

Artifacts produced during a run also appear with that run's evidence, so the timeline remains the fastest route when you already know the execution.

Ownership and lineage

Artifacts are project resources, but access also follows the producing principal's artifact space. A run-produced artifact records the run, step, worker job, and attempt that created it.

Workers publish through an active claim so Mobius can derive that lineage. A normal user or API client cannot attach an unrelated file to a run and make it look like genuine output.

Storage and deletion

Artifact bytes count toward the project's storage quota. The artifacts page shows current usage before the list.

Deleting an artifact removes its stored bytes and frees quota. Mobius keeps enough metadata for audit and run-history views, so deletion does not rewrite the historical fact that the run produced a file.

Source events

Creating an artifact emits artifact.created. A later loop can react to that event when file publication should start another process.

Next

• Do filesystem work in managed environments.
• Publish and download files through the Artifacts API.
• Use artifact commands from the CLI command reference.
• Inspect artifacts alongside runs.