Bug Description
Feature request: Artifact tool can publish and update, but cannot delete
What I hit
I published an artifact from Claude Code. Shortly after, I needed to take it
down: the content was covered by a confidentiality clause and should not have
left my machine.
The Artifact tool only exposes action: "publish" and action: "list". There
is no delete or unpublish. I had to open a browser, go to
claude.ai/code/artifacts, and remove it there.
Workaround
Republished the same file_path with a blank page. That neutralises the content
immediately and keeps the same URL, but the artifact still exists and still
shows up in the gallery. Actual deletion still required the web UI.
Why it matters
Publishing from the CLI is one tool call. Retracting is a context switch to the
browser. That asymmetry bites hardest exactly when speed matters — the moment
you realise something shouldn't be published. NDA / embargoed / competition-
confidential material is the common case, and "go delete it in the web UI" is
the wrong answer at that moment.
Request
Add action: "delete" (and/or "unpublish") to the Artifact tool, accepting
either url or file_path, mirroring how the update flow already resolves an
existing artifact.
Environment Info
- Platform: linux
- Terminal: wsl-kali-linux
- Version: 2.1.227
- Feedback ID: 83163827-3337-46bb-8692-e18bb1a8d7e6
Errors
Bug Description
Feature request: Artifact tool can publish and update, but cannot delete
What I hit
I published an artifact from Claude Code. Shortly after, I needed to take it
down: the content was covered by a confidentiality clause and should not have
left my machine.
The Artifact tool only exposes
action: "publish"andaction: "list". Thereis no delete or unpublish. I had to open a browser, go to
claude.ai/code/artifacts, and remove it there.
Workaround
Republished the same file_path with a blank page. That neutralises the content
immediately and keeps the same URL, but the artifact still exists and still
shows up in the gallery. Actual deletion still required the web UI.
Why it matters
Publishing from the CLI is one tool call. Retracting is a context switch to the
browser. That asymmetry bites hardest exactly when speed matters — the moment
you realise something shouldn't be published. NDA / embargoed / competition-
confidential material is the common case, and "go delete it in the web UI" is
the wrong answer at that moment.
Request
Add
action: "delete"(and/or"unpublish") to the Artifact tool, acceptingeither
urlorfile_path, mirroring how the update flow already resolves anexisting artifact.
Environment Info
Errors