{"version":"2.1.286","anchor":"webfetch-artifact-read-consent-other-users-reads-can-be-us","canonical_anchor":"webfetch-artifact-read-consent-other-users-reads-can-be-us","heading":"Permission prompts for fetching other people's artifacts are decided differently","tier":"notice","area":"Web Fetch","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/webfetch-artifact-read-consent-other-users-reads-can-be-us","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Permission prompts for fetching other people's artifacts are decided differently\n\nWhen WebFetch reads an artifact made by someone else, Claude Code now weighs more settings in deciding which permission prompt to show\n\n**Unclear.** It is unclear what the new settings default to and how the prompts you see differ.\n\n**What**\n\nWhen the WebFetch tool reads an artifact created by another person, Claude Code decides whether and how to ask your permission. That decision now takes into account a setting that can limit such reads to you alone. The note about the artifact coming from outside your organization is now added only when the decision is about that case. The order of the checks has also changed.\n\n**Why**\n\nThis changes which permission prompts you may see when Claude fetches other people's artifacts.\n\n- Area: Web Fetch\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}