Claude Code v2.1.223 ·
Artifact explainer must justify having no visual
Artifact explainers must now name a diagram type or spell out why there is no visual.
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.223,
In DevelopmentSection of the release
The visual field became a discriminated union requiring a reason when absent; whether this schema is live could not be resolved.
What
The synthesis visual field can no longer simply be null; a missing visual has to state why. The activation state of this schema could not be resolved.
Details
visual is now a discriminated union carrying a delta_diagram, flow, or before_after- the alternative is an explicit
{kind: "none", reason} whose reason must be non-blank - renderers switch on
kind === "none" instead of a null check
Evidence
the no-visual reason must not be blank
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.223 →
