Visual outputs agents produce in CRHQ — code files, HTML pages, documents, images, and interactive apps. Every artifact is versioned, shareable, and editable in place.
Artifacts are visual outputs that agents produce during conversations. They appear in a dedicated panel and can be previewed, edited, versioned, shared, and revisited at any point in the session.
When an agent creates something visual — a code file, an HTML dashboard, a document, a diff — it renders as an artifact in the panel. This separates the "output" from the "conversation" for a cleaner experience and gives every artifact a persistent identity that survives edits, restarts, and re-shares.
The artifact panel appears on the side of the conversation when an artifact is created. It supports:
⋯ overflow menu and the action buttons reflow into a second row alongside the Preview/Code toggleAgents create artifacts when they:
Tapping the × on an artifact tab closes the artifact in the panel only — it does not delete it. The artifact stays in the database with its full version history and any active share link intact. You can re-open it later from the Session Details panel (see below).
To permanently delete an artifact (with all versions and any active share), use Session Details → Artifacts tab → ⋯ menu → Remove forever. There's an explicit confirm step — deletion cannot be undone.
Tap the summary icon at the bottom of the conversation to open Session Details. This panel has two tabs:
⋯ menu on each row exposes Open, Open & share, Version history, and Remove forever.See Session Details for the full walkthrough.
Every change to an artifact creates a new version automatically. Edits made by an agent count, edits you make in the editor count, and renames or content swaps all bump the version. Older versions are never overwritten — you can preview them, compare modes (rendered vs raw source), and restore any of them as a new version. See Versioning & History.
HTML, React, and image artifacts can be shared via a public URL. The same artifact always uses the same share URL — even after you edit it — and link-preview cards (WhatsApp, Slack, iMessage, Discord, Twitter) now show the artifact's real title and description. Lifetime visit counts persist across revoke/recreate. See Sharing Artifacts.
Not everything becomes an artifact. Short code snippets, explanations, and text responses stay inline in the conversation. Artifacts are for: