Assets, provenance, and versions

Assets is the project library for saved artifacts and files, each carrying creator, source, context, and version provenance.

Open beta guideJump to first section

Artifact or file

An artifact is a durable document produced by a capability, tool, or agent. A file is a durable non-document output such as a generated image, logo, SVG, or upload. Both live in Assets.

Drafts stay private to their Chat

A capability-created document begins as a draft. It remains addressable from its message but does not enter Assets, search, MCP reads, project summaries, or downstream context until Save to Assets. Saving promotes the same record rather than copying it.

Provenance

Saved outputs record whether they came from a user, tool:<id>, or agent:<id>, plus the owning Chat/task, selected model or engine, references, and revisions. Image files preserve prompt, model, ratio, and reference lineage.

Local and cloud storage

Cloud Assets follow project roles, review-target rules, and storage quotas. Machine-local projects keep artifact metadata and file bytes on the Mac. Creating a collaborative cloud copy transfers bounded metadata and leaves local Asset bytes behind until the user selects what collaborators need.