{"version":"2.1.271","anchor":"artifact-publish-flow-file-path-favicon-now-required-no","canonical_anchor":"artifact-publish-flow-file-path-favicon-now-required-no","heading":"Artifact publish flow: file_path + favicon now required, no inline content param","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-publish-flow-file-path-favicon-now-required-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact publish flow: file_path + favicon now required, no inline content param\n\nPublishing an artifact now requires saving it to an .html file and supplying file_path plus a one-or-two-emoji favicon\n\n**What**\n\nThe 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:\n\n- Claude must write the page to an `.html` file first\n\n- The publish call must then pass `file_path` pointing to that file\n\n- The publish call must also pass a `favicon`, made of one or two emoji\n\n- A variant of the flow also supports starting from a `type_url`\n\n**Why**\n\nThis 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.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}