{"version":"2.1.323","anchor":"artifact-url-tools-now-route-through-a-permission-dialog-wra","canonical_anchor":"artifact-url-tools-now-route-through-a-permission-dialog-wra","heading":"Permission checks for artifact links go through a different step","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/artifact-url-tools-now-route-through-a-permission-dialog-wra","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Permission checks for artifact links go through a different step\n\nWhen the artifact tool is given an artifact link, its permission check now goes through a separate step that handles the permission dialog\n\n**Unclear.** What this changes about the permission prompt you see for artifact links is not stated.\n\n**What**\n\nBefore Claude Code lets a tool run, it checks whether it needs your permission. For the artifact tool, when the input is a link that can be read as an artifact URL, that check now goes through a separate step that handles the permission dialog. Other inputs are checked as before.\n\n**Why**\n\nThe permission prompt you see when Claude works with an artifact link may differ from before.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}