{"version":"2.1.268","anchor":"artifact-fetch-ask-permission-message-wording-changed-from","canonical_anchor":"artifact-fetch-ask-permission-message-wording-changed-from","heading":"Artifact fetch \"ask\" permission message wording changed from URL-fetch framing to artifact-read framing","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/artifact-fetch-ask-permission-message-wording-changed-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Artifact fetch \"ask\" permission message wording changed from URL-fetch framing to artifact-read framing\n\nThe approval prompt for fetching a claude.ai artifact now describes it as reading the artifact, not fetching a URL\n\n**What**\n\nWhen Claude Code asks for permission to fetch a claude.ai artifact, the wording of the prompt changed. It previously said an existing \"ask\" rule covers fetching the URL; it now says the rule covers reading the artifact.\n\n**Why**\n\nThe new wording more accurately describes what's actually happening (reading an artifact) rather than framing it as a generic URL fetch, which should make the permission prompt less confusing.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}