HTML Artifacts

Purpose

Use HTML as a working canvas when the user needs to understand, compare, tune, review, or share non-trivial agent output. The goal is not decoration; it is higher-bandwidth human review.

When To Use

Prefer an HTML artifact for:

• Implementation plans, feature specs, architecture maps, and long technical explainers.
• PR or code-review explainers with annotated diffs, severity labels, and data-flow or control-flow diagrams.
• Design exploration grids, mockups, component inventories, and design-system summaries.
• Research, status, incident, or leadership reports that benefit from scannable sections and visuals.
• One-off editors or playgrounds for hard-to-describe choices: priorities, config, prompts, colors, easing curves, crop regions, schedules, regexes, labels, dataset curation, or annotations.

Use Markdown or chat instead for: