What
A delete now checks whether it is running in a cloud session first, and if so denies with a message telling the model not to retry and pointing you at claude.ai or /artifacts on your own machine.
Details
- The check is a runtime pair of helpers, not an environment variable or named flag, so what puts a session into that state is decided outside the CLI.
Evidence
This cloud session cannot delete Artifacts right now
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/artifacts
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 Connect Claude Code to an LLM gateway touched a line naming /artifacts after this was published.
| `400` errors on every request, in the gateway's own words rejecting a tool's input schema or its `pattern`, on Claude Code v2.1.265 through v2.1.267 | In a gradual rollout on those versions, the [Artifact tool](/docs/en/artifacts#availab…llm-gateway-connect see the edit
Confirmed since
Anthropic's documentation has since written up /artifacts, on Error reference.
Claude tried to publish an [artifact](/docs/en/artifacts) from a file whose bytes don't decode as text, or whose text already contains the replacement character `U+FFFD`, so Claude Code refused the publish before uploading anything. The me…errors 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 /artifacts, on Error reference.