{"version":"2.1.282","anchor":"artifact-tool-comments-action-no-longer-covered-by-a-whole","canonical_anchor":"artifact-tool-comments-action-no-longer-covered-by-a-whole","heading":"Artifact comments need their own approval even when the whole tool is allowed","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/artifact-tool-comments-action-no-longer-covered-by-a-whole","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Artifact comments need their own approval even when the whole tool is allowed\n\nA blanket allow rule for the artifact tool no longer auto-approves its comments action, which now gets its own permission check\n\n**Unclear.** The artifact tool's name as users see it, and whether it is available to everyone, is not known.\n\n**What**\n\nThe artifact tool's comments action is now one of the actions that a permission rule allowing the whole tool does not cover. Such an allow rule lets Claude use a tool without asking you each time. Comments now get their own permission decision, the same way reading page data and verifying already did.\n\n**Why**\n\nReading or posting comments on an artifact now needs its own approval, even if you have allowed the rest of the artifact tool.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}