{"version":"2.1.239","anchor":"remote-sessions-keep-watching-an-artifact-for-comments-after","canonical_anchor":"remote-sessions-keep-watching-an-artifact-for-comments-after","heading":"Remote sessions keep watching an artifact for comments after they stop running","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-sessions-keep-watching-an-artifact-for-comments-after","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote sessions keep watching an artifact for comments after they stop running\n\nRemote sessions can keep a durable artifact watch that wakes them for republishes and comments.\n\n**What**\n\nWatching a published page for republishes and comments now has three states rather than on or off. In a remote session it is \"durable\": the artifact service holds the subscription and wakes the session for republishes and comments addressed to Claude. The old text telling the model that watching is not supported from a remote session is gone.\n\n**Details**\n\n- Durable mode applies when `CLAUDE_CODE_REMOTE` is set; otherwise the mode is \"live\" or \"none\", and the local watch registration only happens under \"live\".\n- New guidance covers a comment thread whose resolve was not confirmed: retry once, and otherwise say so in a reply on the thread.\n\n**Evidence**\n\n`durable wake subscription held by the artifact service`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}