{"version":"2.1.287","anchor":"artifact-comments-refuse-when-page-comment-threads-cant-be","canonical_anchor":"artifact-comments-refuse-when-page-comment-threads-cant-be","heading":"Artifact comment replies and resolves stop when thread settings can't be read","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/artifact-comments-refuse-when-page-comment-threads-cant-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Artifact comment replies and resolves stop when thread settings can't be read\n\nReplying to or resolving an artifact comment now stops with a message, posting nothing, when Claude Code can't tell if the page keeps its own threads\n\n**Unclear.** What causes the comment-thread check to fail was not stated.\n\n**What**\n\nWhen Claude Code replies to a comment on an artifact or marks one resolved, it first checks whether the page keeps its own comment threads. If it cannot read that, it now refuses with a message saying nothing was posted or resolved. It also asks for the page to be read back.\n\n**Why**\n\nIf this check cannot be completed, replies and resolves now fail safely. Nothing gets posted or resolved in the wrong place.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}