Artifact publish refuses every artifact-type instance (Design, Design System), even for the owner

Status Open
Reported on v2.1.300
Maintainer reply None cached
Activity 0 comments · opened Oct 15, 2026

Problem

Claude Code's Artifact tool can read a Design System or Design canvas the user owns (read with paths
returns project/design-system.json, tokens.json, README.md), but any publish to it is refused:
"the Artifact being updated was created from an Artifact type, and no file or page can be published
to it from this session ... retrying cannot help". Delete on the same artifact succeeds.

What was tried (Claude Code 2.1.300, Linux terminal)

  1. Publish with url + root + files limited to project/ paths, following the type's own SKILL.md

("Your Artifact tool takes root (Cowork, Claude Code)") -> refused.

  1. Same after /design-login and /design consent -> refused; DesignSync list_projects returns [].
  2. The same design system's index records an earlier write "via Claude Code", so some client can write it.

Expected

The owner's Claude Code session can publish project/ files into a typed instance, as the type's
SKILL.md describes, or the docs say which client may.

Use case

Scientific figures: code builds and revises the style (tokens) and figures; the user polishes in
Desktop. Without write access every change becomes a manual paste into the item's chat.

Related: #99534 (read side).

View original on GitHub ↗