[BUG]

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?

I published a private Artifact and updated it (via the same session, same file path, targeting the existing URL). Everything I can check server-side confirms the update took:

Direct fetch of the artifact's raw content shows the current version
The Artifact listing (action: "list") shows updated on the correct, current date
But the actual rendered page at the artifact's URL still shows an older version, days behind. I've ruled out client-side caching pretty thoroughly:

Hard refresh (Ctrl+Shift+R) — no change
Brave Private Window — still stale
A cache-busting query string appended to the URL — still stale
A completely different browser (Chrome) — still stale
A different device entirely (phone, on mobile data, not the same wifi) — still stale
Since it's stale across every browser, every network, and even a private/incognito context that shouldn't share cache with anything, this points to a caching or propagation issue in how the Artifact viewer serves the page, not a client-side problem.

Happy to provide the artifact ID/URL directly if a maintainer needs it to investigate — didn't want to post it in a public issue since the content is private.

What Should Happen?

Republishing an Artifact to an existing URL (via url param, same file path) should update what's served at that link within a reasonable time — a few minutes at most — regardless of browser, cache state, or network. Since the platform's own metadata and a direct content fetch both already show the update as live, the rendered page at the public URL should reflect that same current version, not a snapshot from several days earlier.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

Publish an HTML file as a new Artifact (via Claude Code's Artifact tool) — get back a shareable URL.
Edit the underlying file, then republish to the same URL (passing the existing artifact's url param) — tool confirms success each time.
Repeat step 2 several times over the course of one session (in my case: 4-5 republishes across roughly an hour, each adding/correcting data).
Independently confirm the latest content actually took: fetch the artifact's raw content directly, and check the Artifact listing's updated timestamp — both reflect the most recent republish correctly.
Open the artifact's URL in a browser.
Expected: page shows the same current content confirmed in step 4.
Actual: page shows a version from several republishes earlier, days out of date.
Try to force a fresh load: hard refresh, private/incognito window, a cache-busting query string on the URL, a different browser entirely, and a different device on a different network (phone, mobile data).
Actual: stale content persists through all of the above — same old version every time.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Code version 2.1.226.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_