Artifact public sharing fails with "unscannable" content scan error
Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 18, 2026
Description
Attempting to make a Claude Code Artifact public (via the share menu) fails
with the following error, even after republishing a new version of the
artifact to force a fresh scan:
{
"error": "frame: public serving requires the served version's content scan to be dispatched (unscannable)",
"reason": "unscannable"
}
Steps to reproduce
- Publish an HTML artifact via the Artifact tool in Claude Code.
- Open the artifact's share menu and attempt to switch visibility to "Public".
- The toggle fails with the "unscannable" error above.
- Republishing the same artifact (new version, same URL) does not resolve it —
the error persists.
Affected artifacts
Reproduced consistently across 6 different self-contained HTML artifacts
published in the same session. Files are static HTML (single file, inline
CSS/JS, embedded font as a base64 data: URI), largest is ~147KB — well
under the documented 16MB artifact size cap, so this does not appear to be
a size-related issue. Happy to share specific artifact URLs privately if
useful for debugging.
Environment
- Claude Code CLI on Windows (win32)
- Issue observed 2026-08-18