Group of 8 Use it now
Artifact publishing now uses a generic icon word instead of a favicon emoji, and reads/lists show whether you can edit a shared artifact
What
- The Artifacts tool's
faviconparameter (an emoji, e.g. "one or two emoji") is deprecated in favor of a newiconparameter 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. - Publishing an artifact no longer requires a favicon at all; only
file_pathis required now. - 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). - 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.
Why
This 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.
Names in the bundleicon
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Manage plugins and connectors touched a line naming icon after this was published.
Apart from the optional icon, everything in an archive must be text in UTF-8. There is no way to ship a script, or any other binary asset such as an image, through the card. File and folder names must be ASCII. Nothing in the archive may s…government/config/plugins-and-connectors see the edit
Confirmed since
Anthropic's documentation has since written up icon, on Configure cloud environments.
Shared environments appear in each member's [environment selector](#configure-your-environment) under an **Organization** heading, after the member's own environments under **Personal**, so a team can standardize on one configuration inste…cloud-environments see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up icon, on Configure cloud environments.