{"version":"2.1.236","anchor":"resuming-a-stopped-artifact-watch-requires-a-turn-you-starte","canonical_anchor":"resuming-a-stopped-artifact-watch-requires-a-turn-you-starte","heading":"Resuming a stopped artifact watch requires a turn you started","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/resuming-a-stopped-artifact-watch-requires-a-turn-you-starte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Resuming a stopped artifact watch requires a turn you started\n\nClaude can only restart a stopped artifact watch during a turn you started yourself.\n\n**What**\n\nIf watching an artifact was deliberately stopped earlier in the session, Claude can only re-arm auto-replies in a turn you initiated. Otherwise the call is denied, with instructions not to retry in the same turn and not to answer the pending comments itself as a workaround; it must list them for you instead. No flag, this is live for everyone.\n\n**Details**\n\n- The denial is recorded as a safety check that the automatic permission classifier cannot approve.\n- Meta messages are marked as tool companions so they are not mistaken for a human-initiated turn.\n- The watch consent prompt was narrowed from \"notifications carry no content\" to \"republish notifications carry no content\", now that comments can also wake a watch.\n\n**Evidence**\n\n`Re-watching an artifact whose watch was stopped this session \\u2014 only a request made in a turn the user started may ask for it`, `only a request made in a turn the user started may ask for it`, `Resuming auto-replies reverses a stop \u2014 only a request made in a turn the user started may ask for it`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}