{"version":"2.1.251","anchor":"read-reply-to-and-resolve-comment-threads-on-published-artif","canonical_anchor":"read-reply-to-and-resolve-comment-threads-on-published-artif","heading":"Read, reply to, and resolve comment threads on published artifacts","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/read-reply-to-and-resolve-comment-threads-on-published-artif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Read, reply to, and resolve comment threads on published artifacts\n\nClaude can read, reply to and resolve comment threads on your published artifacts.\n\n**What**\n\nA new tool works on comment threads left by viewers of a published artifact. It supports reading threads (paged by thread id and cursor), posting a reply, and marking a thread resolved. Resolving is refused entirely in plan mode, and reading comments after an unattended new-comments notification asks you to confirm even in channels that normally auto-allow.\n\n**Details**\n\n- Replies are validated before sending: invisible and control characters are rejected, byte length is capped, and repeated identical answers are blocked.\n- Comment text comes from artifact viewers, so the confirmation prompt names that explicitly when the read was triggered by a notification rather than by you.\n\n**Evidence**\n\n`Claude wants to read the comment threads on ${ro(o)} \u2014 prompted by the new-comments notification; comment text is written by artifact viewers`\n\n- Area: Artifacts\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 5\/5"}