{"version":"2.1.233","anchor":"auto-reply-stands-down-when-the-comment-thread-was-already-a","canonical_anchor":"auto-reply-stands-down-when-the-comment-thread-was-already-a","heading":"Auto-reply stands down when the comment thread was already answered","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/auto-reply-stands-down-when-the-comment-thread-was-already-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Auto-reply stands down when the comment thread was already answered\n\nAuto-reply stays quiet when someone has already answered the artifact comment thread.\n\n**What**\n\nWhen a reply is attempted on an artifact comment thread that someone already answered, Claude Code no longer posts, and reports \"reply not posted (thread already answered)\".\n\n**Details**\n\n- The reply result can carry an `already_answered` flag, producing a new outcome `answered_post_time` alongside the existing `answered_elsewhere` and `summon_foreign`.\n- The suppression is recorded on the `artifact_comments_autoreact` metric as `edit_reply_stood_down_post_time` and `answered_post_time_notice_suppressed`.\n\n**Evidence**\n\n`reply not posted (thread already answered)`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}