Skip to main content
HTML artifacts are interactive pages saved in a Task: reports, charts, comparisons, plans, and explainers. Unlike a passage in chat, the page remains in the Artifacts panel for later use and revision.

Create and Open a Page

Ask an agent for an HTML artifact. For example:
Create an interactive HTML report comparing the approaches, with a table of trade-offs and expandable details.
Open the result from Artifacts, or ask the agent to show it inline in chat. An inline preview’s Expand control opens that captured version in its own panel. Type @ and choose it from Artifacts when asking for changes. HTML artifacts are folders with an index.html file and supporting styles, scripts, images, or data. You do not have to assemble these yourself: describe the result you want to the agent.

Use and Review the Page

Buttons, filters, tabs, and other page interactions can work directly in the preview. Links to websites ask for confirmation before opening outside Traycer. Page content runs separately from the app; it does not have direct access to your files or signed-in session. Interactions can use online resources, so a downloaded page may still need an internet connection. To request a targeted change, open the latest version and turn on Comments. Select an element or text to leave a thread, or use Send to chat to attach the selection to an existing agent chat’s draft. Send the message when you’re ready. Turn comments off to use the page normally again. See Comments.

Versions and Downloads

Use the Latest / Version control in the page toolbar to preview saved versions. Choose Older versions to go further back, and Latest to return to the current page. Selecting a version does not replace the live artifact. Comments attach to the latest page, not a historical preview. Download ZIP saves the version you’re viewing, including its supporting files. Extract the ZIP to inspect or reuse the page and its files outside Traycer. ZIP downloads support up to 64 MB of files. This is a page download, not a PDF or screenshot.

Interactive Apps in Chat

An agent can also display an interactive app supplied by a connected MCP server directly in chat. These MCP Apps are different from saved HTML artifacts: they belong to the tool response that produced them. Use Open full screen to give an app more room, then Exit full screen or Esc to return to chat. When an app needs approval for a tool action, review the request before approving it. App downloads also ask for confirmation. A tool response is not automatically a saved artifact; ask the agent to create a separate deliverable if you need one in Artifacts.