{"version":"2.1.295","anchor":"artifact-tools-no-longer-depend-on-a-gate-d","canonical_anchor":"artifact-tools-no-longer-depend-on-a-gate-d","heading":"Permission checks for artifact tools now always apply","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/artifact-tools-no-longer-depend-on-a-gate-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Permission checks for artifact tools now always apply\n\nPermission prompts and read checks for artifact tools no longer depend on an earlier condition and now always apply\n\n**What**\n\nClaude Code's tools for reading and saving artifacts used to apply their permission prompts, and their read-only check for reading artifact comments, only when a separate condition was true. That condition has been removed, so these checks now always apply.\n\n**Why**\n\nIn practice, the approval step for artifact tools now runs in every case. You may see permission prompts for artifacts where you did not see them before.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}