Files and Artifacts

How Consuelo OS tracks generated files and outputs.

Files and artifacts

Consuelo OS treats generated files as artifacts.

An artifact is an app-native record with storage behind it. The record tracks who created it, which skill created it, what source records were used, where the output is stored, and what version it belongs to.

Files are bytes. Artifacts are product records.

A report in a folder is just a file. A report artifact is a tracked output with ownership, provenance, status, and storage metadata.

This distinction matters because agents generate a lot of output. Without artifact records, important work disappears into local folders, chat transcripts, or temporary files.

Artifact lifecycle

skill produces output
  -> OS creates artifact metadata
  -> OS stores bytes locally or in cloud storage
  -> OS links artifact to execution
  -> user or team can inspect the result later

Artifact record shape

Field	Purpose
id	Stable artifact identifier.
workspaceId	Workspace that owns the artifact.
createdByUserId	User who requested or created it.
skillExecutionId	Execution that produced it.
skillName	Skill that created it.
title	Human-readable name.
type	Report, brief, draft, export, document, page, or other category.
format	Markdown, HTML, JSON, CSV, image, or app-native.
status	Draft, published, archived, or deleted.
storageMode	Local, cloud, or external.
storageKey	Path or object key for stored bytes.
sourceObjectRefs	Structured records used to create the output.
traceId	Trace linking artifact to logs and execution.

Local storage

Local OS stores artifact bytes under the local OS home and stores metadata in SQLite.

Local storage is useful for development, solo users, internal builders, and self-hosted installs.

Cloud storage

Cloud OS stores artifact bytes in cloud storage and records metadata in the app.

Cloud storage is required for shared team workflows, app-visible artifacts, hosted observability, and sellable team workspaces.

Formats

Artifacts can be Markdown, HTML, JSON, CSV, images, app-native records, or other durable outputs. The format is secondary. The artifact record is the product layer.

Related

• Create your first artifact
• Observability
• Local and cloud