{"version":"2.1.223","anchor":"clearer-wording-when-claude-is-not-activated-on-a-comment-th","canonical_anchor":"clearer-wording-when-claude-is-not-activated-on-a-comment-th","heading":"Clearer wording when Claude is not activated on a comment thread","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/clearer-wording-when-claude-is-not-activated-on-a-comment-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Clearer wording when Claude is not activated on a comment thread\n\nWhen a comment reply can't post, you get a clearer explanation instead of a misleading one about thread state.\n\n**What**\n\nThe Artifact tool now explains why a reply could not be posted instead of implying the thread state was the cause.\n\n**Details**\n\n- Both the reply failure text and the action description were rewritten.\n- The new wording states that activation is per artifact version and can be cleared by deactivation, republish or rename.\n- It states plainly that this is unrelated to whether a thread is resolved.\n- It instructs Claude not to assert a specific reason for the failure.\n\n**Evidence**\n\n`resolved threads still accept replies`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}