What probably matters to youSection of the release
What
Artifacts can now include a new icon field: a single short generic word (e.g. "chart", "calendar") meant as a plain page-type signifier, separate from the existing favicon. It's persisted across redeploys like the favicon, and is explicitly ignored on artifacts created from an Artifact type.
When publishing an artifact, if the publish endpoint rejects the request because of an unknown icon or deadline field, Claude Code now automatically strips just that field and retries, instead of failing outright. This generalizes what used to be a retry that only handled a rejected deadline field, so the retry loop now keeps stripping whatever field gets rejected until nothing more is rejected.
The notice shown when extra fields are supplied on an Artifact-type create (which are ignored) now refers to the favicon/description as starting from "the type's ... emoji" instead of "icon", to avoid confusion with the new icon field.
Why
This gives artifacts a lightweight, generic type indicator distinct from their favicon, while making publish/deploy more resilient to servers rejecting fields Claude Code doesn't yet know are unsupported, and avoids the two similarly-named concepts (favicon vs. the new icon) being confused in user-facing text.
