{"version":"2.1.239","anchor":"comment-replies-from-a-cowork-session-are-no-longer-refused-","canonical_anchor":"comment-replies-from-a-cowork-session-are-no-longer-refused-","heading":"Comment replies from a Cowork session are no longer refused outright","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/comment-replies-from-a-cowork-session-are-no-longer-refused-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Comment replies from a Cowork session are no longer refused outright\n\nReplying to artifact comments from a Cowork session now goes through normal approval instead of being refused.\n\n**What**\n\nPosting a reply to a comment on a shared artifact from a Cowork frame used to be denied with a message saying the approval card could not be answered in that session. That refusal is gone, and replies now go through the normal approval request with one reason naming the thread and who will see it.\n\n**Details**\n\n- The Cowork-specific reason text was dropped along with the deny branch, so there is one code path for all sessions.\n- Replies still require confirmation; what changed is that the confirmation can now actually be given.\n\n**Evidence**\n\n`requires confirmation`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}