Group of 2 You'll notice
Artifact watch/subscribe no longer claims a republish elsewhere triggers a notification; it now tracks versions silently and warns on the next read
What
The help text and behavior around watching an Artifact (a published file Claude Code can track for changes) has changed:
- The tool description no longer says that a republish from elsewhere "arrives as a notification telling you to re-read it before editing."
- It now says a republish elsewhere "starts no turn and sends no notification."
- Instead, Claude Code silently keeps track of the artifact's version in the background.
- The next time the artifact is read or a publish is attempted, the result is prefixed with a warning telling Claude a newer version exists, and instructing it to re-fetch the URL and merge its edits onto that version.
- The description also explains what to do if a publish is rejected because the artifact changed underneath it.
Why
Previously the description implied a republish elsewhere would actively wake the session with a notification, which wasn't accurate. The new wording sets correct expectations: nothing interrupts the current turn, but the next read or publish attempt will catch Claude up and prompt it to merge its changes onto the latest version instead of overwriting it.