[BUG] Artifact sharing fails with "this version can't be shared publicly" even after republishing

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Description

When trying to enable public link sharing on a published Artifact, I get the following error:

▎ This version can't be shared publicly. Publish a new version or change the shared version, then try again.

What Should Happen?

Expected behavior

The artifact should either share successfully, or the error message should point to something actionable I can actually fix (right now it suggests "publish a new version," which I did, with no change in outcome).

Error Messages/Logs

This version can't be shared publicly. Publish a new version or change the shared version, then try again.

Steps to Reproduce

Steps to reproduce

1. Claude Code published an HTML artifact via the Artifact tool.
2. Opened the artifact page and used the share menu → "Anyone with the link".
3. Got the error above.
4. Asked Claude to republish the same artifact (same file path, new version) to see if a fresh version would resolve it.
5. Tried sharing again — same error persisted.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.217 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Additional context

The artifact is an internal technical document (a study + migration plan for a module of an internal government system) styled with an "official document" visual theme (institutional color palette, references to the organization's internal system name). It's possible the public-sharing check is flagging this styling/content as impersonation of a real organization, even though it's just internal engineering documentation about our own codebase — but I have no way to confirm this from the client side.