{"version":"2.1.268","anchor":"comment-thread-repliesresolves-now-special-case-artifact-pa","canonical_anchor":"artifact-auto-react-now-recognizes-when-the-page-itself-owns","heading":"Artifact comment threads now recognize pages that manage their own threads","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/comment-thread-repliesresolves-now-special-case-artifact-pa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Artifact comment threads now recognize pages that manage their own threads\n\nClaude Code now detects artifact pages that own their own comment threads and stops trying to auto-react, reply, or resolve on them\n\n**What**\n\n- Artifact auto-react logic now checks for `pageOwnsThreads`: when a thread reports this, auto-react is declined with a \"blocked\" reason, and a new telemetry event (`page_owns_threads`, or `page_owns_threads_notice_suppressed` if the notice can't be shown) is emitted instead of treating it as a normal deactivation.\n\n- A new terminal reason, `page_owns_threads`, produces messages like \"reply not posted (the page keeps its own comment threads)\" and \"not resolved (the page keeps its own comment threads),\" instead of falling through to the generic \"needs thread activation\" message.\n\n- The tool results for posting a reply or resolving a thread now special-case `page_owns_threads === true`, telling the model that the target page manages its own comment threads and that replying or resolving through the session's relay tool is a no-op it shouldn't retry.\n\n**Why** Some artifact pages handle their own comments outside of Claude Code's relay. This change stops Claude from repeatedly trying (and failing) to react to, reply to, or resolve threads on those pages, and gives a clear explanation instead.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}