[BUG] Shared Artifact links get pinned to a stale version — no way to keep them tracking "Latest"

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?

When an Artifact is shared publicly ("Anyone with the link"), the "Shared version" selector locks to whatever version was current at share time. Republishing the same artifact (same file path / same URL, via the Artifact tool in Claude Code) creates a new version, but the publicly shared link keeps resolving to the old pinned version — viewers do not see the update.

Trying to fix this in the Share dialog hits a dead end: selecting "Latest" is blocked with the error "Can't switch to Latest while shared publicly. Change who has access first." The only workaround is switching General access to private, selecting Latest, then switching General access back to public — and this has to be repeated by hand after every single redeploy.

This defeats the purpose of an artifact meant to be refreshed automatically — e.g. an agent re-running a data pipeline and republishing a live dashboard. Right now every refresh silently stops updating for anyone who already opened the link, until the owner manually redoes the private→Latest→public dance.

What Should Happen?

One of the following would fix it:

Remove artifact versioning entirely (or make it opt-in) — most users republishing an artifact just want the shared link to always show current content, and don't need a retained version history.
Allow selecting "Latest" as the shared version while the artifact is already shared publicly — drop the requirement to temporarily revoke public access first.
Expose a way for Claude Code (the Artifact tool) to set/keep the shared version pinned to "Latest" programmatically after a redeploy, so an agent can refresh a public artifact end-to-end without a human having to open the Share dialog each time.
Any of the three would unblock using shared Artifacts as live, agent-refreshed dashboards instead of one-off static snapshots.

Error Messages/Logs

In the Share dialog, "Shared version" dropdown, attempting to select "Latest" while General access = "Anyone with the link":

Can't switch to Latest while shared publicly. Change who has access first.

Steps to Reproduce

1. In Claude Code, use the Artifact tool to publish an HTML page (e.g. a dashboard). Note the URL.
2. Open the artifact page on claude.ai, click Share, set General access to "Anyone with the link". Copy the link and confirm it loads for a signed-out/incognito view.
3. Back in Claude Code, edit the source file and call Artifact again with the same file_path (and, if not in the original conversation, the same url) to redeploy — this creates a new version (e.g. Version 17 → Version 18).
4. Reload the previously-copied public link. Actual: it still shows the old version's content (pinned version, e.g. "Version 17"), not the new one just published.
5. Open Share again, look at the "Shared version" dropdown — it shows the old pinned version, not the latest.
6. Try clicking Latest in that dropdown. Actual: blocked with "Can't switch to Latest while shared publicly. Change who has access first."
7. Expected: the publicly shared link should always resolve to the latest published version by default, with no manual re-pinning step required after each redeploy.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.220 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_