{"version":"2.1.274","anchor":"artifact-live-subscribe-republish-handling-no-longer-directl","canonical_anchor":"artifact-live-subscribe-republish-handling-no-longer-directl","heading":"Artifact live-subscribe republish handling no longer directly composes a re-read prompt","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-live-subscribe-republish-handling-no-longer-directl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact live-subscribe republish handling no longer directly composes a re-read prompt\n\nLive artifact republish updates no longer inject a re-read prompt message, just log it passively\n\n**What**\n\nWhen a live artifact Claude Code is watching gets republished elsewhere, the handler used to build a message telling Claude the artifact appears to have been republished and should be re-read before editing, and queue it as a task notification. It now instead just records that the new version was heard and logs telemetry, without composing or sending that message.\n\n**Why**\n\nThis is consistent with the shift to passive version tracking: rather than actively interrupting with a re-read prompt each time, the update is recorded quietly and surfaced differently.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}