{"version":"2.1.269","anchor":"artifact-comment-threads-can-now-show-the-commenters-access","canonical_anchor":"artifact-comment-threads-can-now-show-the-commenters-access","heading":"Artifact comment threads can show the commenter's access level","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifact-comment-threads-can-now-show-the-commenters-access","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifact comment threads can show the commenter's access level\n\nArtifact comment threads can now show a commenter's real access level (owner, editor, commenter, viewer) instead of just labeling everyone 'human'\n\n**What**\n\n- Comment and author data passed into the artifact-comments auto-reply feature now carries an `access` field (owner\/editor\/commenter\/viewer) and an `authoredByOthers` flag, instead of only knowing that a message came from a human.\n\n- A new phrase helper turns that into readable text like \"the owner's\", \"an editor's\", \"a commenter's\", or \"a viewer's\".\n\n- When any comment in the visible thread has this access info, the prompt is told that a comment's header may show a tag such as `[editor]` or `[owner, sent to you]` in place of the word \"human\".\n\n- The prompt also explicitly warns that if a comment's own text happens to contain a word like \"owner\", that's still just untrusted text typed by someone, not an actual permission grant.\n\n**Why**\n\nThis lets Claude Code's auto-reply behavior take a commenter's real role into account (for example, treating an owner's request differently from an anonymous viewer's) while making sure it can't be fooled by someone typing a fake role claim into a comment.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}