You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.271,
ImprovementsSection of the release
What
The publish action for artifacts (self-contained pages Claude can build, like a small web app) no longer accepts the page content directly as a parameter. Instead:
Claude must write the page to an .html file first
The publish call must then pass file_path pointing to that file
The publish call must also pass a favicon, made of one or two emoji
A variant of the flow also supports starting from a type_url
Why
This changes how artifacts get published: rather than sending content inline in one step, Claude writes a file and references it, and every published page now gets an emoji favicon. This mainly affects the internal mechanics of publishing, but it means a published page always has a favicon set.
