{"version":"2.1.275","anchor":"icon-field-replaces-deprecated-favicon-in-artifact-publi","canonical_anchor":"artifact-listread-responses-now-expose-per-artifact-edit","heading":"Artifacts tool: icon replaces favicon, and read\/list report editing access","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/icon-field-replaces-deprecated-favicon-in-artifact-publi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifacts tool: icon replaces favicon, and read\/list report editing access\n\nArtifact publishing now uses a generic `icon` word instead of a favicon emoji, and reads\/lists show whether you can edit a shared artifact\n\n**What**\n\n- The Artifacts tool's `favicon` parameter (an emoji, e.g. \"one or two emoji\") is deprecated in favor of a new `icon` parameter that takes a single descriptive word like chart, calendar, recipe, code, or map instead of an emoji, and must not be a product or brand name.\n\n- Publishing an artifact no longer requires a favicon at all; only `file_path` is required now.\n\n- The publish result now reports whether the icon was accepted, dropped by the server, fell back to the old favicon emoji, or was never sent, via new response fields (`iconDropped`, `icon`, `faviconSent`).\n\n- Reading or listing artifacts now reports whether you have edit (\"writer\") access to a shared artifact. Only artifacts you can write to can be updated directly; otherwise Claude has to publish a separate copy. Artifacts shared from another organization may be missing from the listing entirely.\n\n**Why**\n\nThis tells Claude up front whether it can update an existing shared artifact or must create a new one, and simplifies icon selection to a plain word instead of picking an emoji.\n\n- Area: Artifacts\n- Names: `icon`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}