Chat Artifacts

🧪 Chat Artifacts is currently in private beta. Some workspaces and roles may not see artifact features yet. If you would like access, reach out to [email protected].

Chat artifacts turn certain generated files and app outputs from Secure Chat into reusable previews that you can inspect, edit, share, and publish.

When an artifact is available, Secure Chat shows an artifact card in the conversation. Select Preview to open the artifact viewer.

Artifact Viewer

The viewer can include:

A Preview tab for the rendered output.
A Code tab for the generated source when code is available.
Version and status details, such as draft or published state.
Publish controls when your workspace and role allow publishing.

Chat artifact viewer showing a rendered HTML landing page in the Preview tab, with Code and History controls and a Publish button.

Version History

For artifacts with multiple versions, select History in the artifact viewer to view past versions and their status, such as draft, published, current, or latest.

To reuse an older version, select Restore as new draft. Restoring does not replace or delete existing versions. Hatz copies the selected version into a new draft that you can review, edit, and publish when ready.

Editing an Artifact

While an artifact is open, it stays attached to your chat. To change it, type a follow-up message in the same conversation describing what you want—for example, "Update the heading and add a summary section"—and Hatz revises the artifact. Each revision is saved as a new version, so your earlier versions stay available in History.

Editing a chat artifact by typing a follow-up request in the chat while the artifact stays attached, with the rendered artifact shown alongside.

Publishing Options

Artifacts can be published with different visibility levels:

Private: available only to signed-in users who have access to the chat context.
Organization: available to members of the current workspace.
External (public link): available to anyone with the link, outside the signed-in app. External publishing is a separate control that is turned off by default and is only available when your workspace and role allow it. Use it only for content that is safe to share publicly.

Choose the narrowest visibility that fits the use case. If an artifact contains client data, internal process details, or sensitive context, keep it private until it has been reviewed.

Publish Artifact dialog showing Private and Organization visibility options for a chat artifact.

Sharing with groups

When you publish an artifact to your Organization, the publish dialog also lets you share it with specific groups. Group sharing is additive: it grants the selected groups access, but it does not restrict who else can open the artifact—everyone in your workspace can still open an Organization-published artifact whether or not you select groups. Group sharing is not available for Private artifacts. You need permission to share with groups, and the groups must already exist.

Admin controls

Administrators control whether artifact authoring and external publishing are available, at the organization, tenant, and role levels. If you expect to author or publish artifacts but the options are missing, an administrator may have these controls turned off for your role. See Custom Roles for the role-level settings.

Supported Outputs

Artifact support is designed for generated outputs such as HTML apps, static React apps, and code or text files that can be previewed. Normal markdown answers and ordinary code blocks are not automatically artifacts.

If you expected an artifact but do not see a preview card, Chat Artifacts may not be enabled for your workspace yet (the feature is in private beta—reach out to [email protected] for access), or the assistant may have returned a normal file or code block instead of an artifact-compatible output.