# Artifacts

**Available in:** Chat, Agent, and Project work. Retained Artifacts have their own identity and sharing controls. Viewing an Artifact does not require access to its producing conversation or grant execution authority.

An Artifact is an intentional custom experience, initially a self-contained HTML, CSS, and JavaScript result. Playbooks retains it under one identity with saved, unchanging checkpoints. Ordinary HTML files, attachments, and Project application previews are separate.

## Create and revisit

When the operator begins a distinct Artifact, it is registered and shown as preparing until the first complete checkpoint is ready. A completed, validated update saves another checkpoint automatically. Failed or incomplete preparation leaves the latest ready checkpoint available. Editing a working file alone does not advance the Artifact.

Open the latest ready version for normal use. History lets an authorized collaborator preview or export an exact older checkpoint. A historical link resolves that saved version rather than silently switching to the latest.

## Restore and export

Restore copies a selected checkpoint's saved editing files into a fresh location in the currently bound source resource, if you also have source read and write access. It preserves existing working files and earlier Artifact history, then appends a new checkpoint. When fuller editing source is unavailable, an HTML-only checkpoint can be restored with that limitation shown.

Export uses the selected retained checkpoint and supported dependencies. It does not export private source material beyond your access. Artifact viewing runs in an isolated browser and gives no connector, Chat execution, or Site management authority. See [sharing](/docs/concepts/sharing) for audiences and [Sites](/docs/sites/overview) for production releases.

## Example: retain a scenario calculator

Ask for a calculator that lets a reader vary assumptions and inspect the outcome. Review the first ready checkpoint, try representative inputs, then request a targeted change such as a clearer explanation of the calculation.

Open the resulting checkpoint and verify both the interaction and its assumptions. Sharing that Artifact gives access to the retained experience, not its producing conversation. See [Sharing](/docs/concepts/sharing); use a [Site](/docs/sites/overview) when you need a separate production destination.

## Choose an audience

Review the Artifact's own sharing controls, independently of the producing Chat, Agent, or Project. Restricted access is for the owner and explicit collaborators; Workspace access admits the applicable authenticated Workspace audience. Public viewing, when enabled, exposes the latest ready checkpoint to anonymous visitors without granting source access or management rights.

Review the experience itself for private information before widening its audience. Disabling public access blocks later anonymous reads but cannot recall content already delivered. See [Permissions](/docs/concepts/permissions) for resource roles and [Sharing](/docs/concepts/sharing) for choosing between collaboration, a retained experience, a template, and a Site.

## Request a focused update

> Update the calculator to show the assumptions beside the result. Keep the existing calculation and label any estimate clearly.

After the update, inspect the new ready checkpoint and try representative inputs. Use [Composer attachments](/docs/composer/controls#attachments) for task references and [Messaging](/docs/composer/messaging) to guide a revision in progress.