{"version":"2.1.271","anchor":"artifact-watch-now-covers-background-sessions-not-just-inte","canonical_anchor":"artifact-watch-now-covers-background-sessions-not-just-inte","heading":"Background sessions can now hold artifact publish\/comment watches","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-watch-now-covers-background-sessions-not-just-inte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Background sessions can now hold artifact publish\/comment watches\n\nBackground sessions can now hold live-update watches on republished artifacts, alongside interactive and SDK sessions\n\n**What**\n\nArtifact publish\/comment \"watches\" (which let a session get live updates when an artifact is republished or commented on) previously explained that only interactive or SDK main-loop sessions could hold one, explicitly excluding background sessions. Now background sessions are included among the sessions that can hold a watch.\n\nA new explanatory status, `publish_context`, tells Claude that print\/cloud\/subagent\/teammate sessions never get live-update notifications when an artifact is republished \u2014 only the main conversation of local interactive, background, or SDK sessions does.\n\n**Why**\n\nThis clarifies, and extends, which kinds of sessions can stay informed when an artifact they care about changes, so background sessions aren't left out of live updates the way they previously were.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}