{"version":"2.1.251","anchor":"clearer-rules-for-activating-and-resolving-comment-threads","canonical_anchor":"clearer-rules-for-activating-and-resolving-comment-threads","heading":"Clearer rules for activating and resolving comment threads","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/clearer-rules-for-activating-and-resolving-comment-threads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Clearer rules for activating and resolving comment threads\n\nClaude now explains how to activate an artifact comment thread it cannot resolve.\n\n**What**\n\nGuidance on artifact comment threads changed. A thread is activated by replying with Send to Claude or by mentioning @claude, and when Claude cannot resolve a thread that was never activated it must leave it open and tell you that a writer can send it to Claude or resolve it in the artifact view. The old wording just told Claude to leave the thread for the commenter.\n\n**Evidence**\n\n`reply on it with Send to Claude`\n\n- Area: Artifacts\n- Names: `@claude`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}