{"version":"2.1.239","anchor":"artifact-failure-messages-point-at-the-tool-s-own-read-actio","canonical_anchor":"artifact-failure-messages-point-at-the-tool-s-own-read-actio","heading":"Artifact failure messages point at the tool's own read action instead of WebFetch","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/artifact-failure-messages-point-at-the-tool-s-own-read-actio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Artifact failure messages point at the tool's own read action instead of WebFetch\n\nFailed artifact publishes now tell Claude to re-read via the artifact tool, not WebFetch.\n\n**What**\n\nWhen a publish or live edit fails, the advice now tells the model to read the page back with the Artifact tool's `read` action rather than fetching the URL, and pasted markdown is rejected with instructions to write HTML markup to a `.html` file first.\n\n**Details**\n\n- The generic publish description is now \"Publish a local file\" instead of naming HTML or Markdown.\n\n**Evidence**\n\n`Write the page as HTML markup to an .html file first (Write\/Edit)`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}