{"version":"2.1.265","anchor":"watch-tool-refuses-to-restart-a-watch-after-an-unapproved","canonical_anchor":"watch-tool-refuses-to-restart-a-watch-after-an-unapproved","heading":"Watch tool refuses to (re)start a watch after an unapproved comment-reply ask in the same session","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/watch-tool-refuses-to-restart-a-watch-after-an-unapproved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Watch tool refuses to (re)start a watch after an unapproved comment-reply ask in the same session\n\nClaude Code won't retry starting an artifact watch after you already declined a related reply request in the same session\n\n**What**\n\nThe `watch` action on artifacts (which lets Claude monitor an artifact, for example to reply to comments on it) now checks whether an earlier request in the same session to let Claude reply to that artifact's comments was declined. If it was declined and hasn't since been separately approved, Claude Code now refuses to start or restart the watch outright, telling the model that only your own next message can trigger asking again - it won't automatically re-ask on its own.\n\n**Why**\n\nThis stops Claude from repeatedly re-requesting a permission you already turned down within a session, closing a path where a declined request could otherwise resurface through a different tool.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}