Artifact share dialog stuck: "shared version" selector greyed out, shows "latest" but sharing fails

[VladMuntianu1]

Description

Published an HTML artifact via Claude Code, tried enabling "anyone with the link" sharing from the artifact page's share menu.

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

The share dialog has a "shared version" field showing "latest", but it's greyed out / not interactive — can't change it to work around the error.

Steps taken to try to resolve, none worked:

• Republishing the same artifact (new version, same file path/URL) — did not resolve it.
• Publishing an entirely new artifact (different file path, brand new URL) — hit the identical error.

Expected behavior

Either the share toggle works on the latest published version, or the version selector in the dialog should be interactive so the shared version can be reselected/reset.

[VladMuntianu1]

Update: found the actual failure via browser DevTools Network tab.

When attempting to enable "anyone with the link" sharing, the page sends:

PATCH .../api/frame/perm/...

which returns 409 Conflict from the server.

This is consistent with what I reported above — it's not a per-artifact or per-account issue. I reproduced the identical 409 on:

1. The original artifact (7 versions in its history)
2. A brand-new artifact published from scratch (fresh history, different URL)

Both hit the same 409 on the same endpoint. This points to a systemic issue with the sharing permission endpoint for /code/artifact/... (Claude Code) artifacts specifically, rather than a state/sync problem on one artifact.

[VladMuntianu1]

Update: isolated the trigger. It's the mermaid diagrams.

Ran two controlled tests:

1. Minimal artifact, plain HTML, no <pre class="mermaid"> content → sharing worked fine, no error.
2. Minimal artifact containing only <pre class="mermaid"> blocks (3 flowcharts, no other content, no custom CSS) → same "This version can't be shared publicly. Publish a new version or change the shared version, then try again." error, same 409 pattern as the original report.

So this isn't about artifact size, complexity, or account state — it's specifically triggered by mermaid diagram content (<pre class="mermaid">) in the artifact. My guess: whatever renders/caches the artifact for the public share view doesn't yet support (or is failing on) the native mermaid rendering path, and the permission PATCH conflicts as a result. Happy to share the exact test artifact HTML if useful for repro.

[bcherny]

Closing as a duplicate of #79824 — please follow and 👍 that issue instead so we can track it in one place. If you think this was closed in error, comment here and we'll reopen.

🤖 Generated with Claude Code

[bcherny]

Closing as a duplicate of #79824 — please follow and 👍 that issue instead so we can track it in one place. If you think this was closed in error, comment here and we'll reopen.

🤖 Generated with Claude Code