Treat other authors' artifacts as untrusted
CHANGELOG · original
Improved the Artifact tool's read of an artifact someone else wrote: the summary now treats the page as untrusted content and flags embedded instructions rather than relaying them Open official changelog ↗ Documentation
Documentation excerpt
Read an artifact shared with you
When someone shares an artifact with you, you can have Claude read it: give Claude its URL, or attach it from /artifacts.
Claude reads a page someone else wrote the way it reads a web page with WebFetch: it gets a summary of what it asked about rather than the raw page, and the summary reports instructions written into the page instead of relaying them. Claude Code also saves the page's full source to a local file, which Claude can open when it needs the exact content, such as to republish the artifact as an editor.
Claude Code asks for your approval before Claude reads the artifact in these cases, in addition to any prompt your permission mode or rules call for:
- Cloud session without network access: for a cloud environment, that's the None level. In auto mode, the classifier can approve instead; in a Cowork session, the approval is yours alone.
- Another organization's public artifact: Claude Code asks you first, even in auto mode. Where Claude Code can't ask you, such as in
bypassPermissionsmode, Claude can't read the artifact. Claude can read these artifacts only while feature-flag fetching is on. - Unconfirmed owner or network setting: when Claude Code can't confirm who made the artifact, or can't confirm a cloud session's network setting, it asks, and your approval covers that one request. In auto mode, the classifier can approve or block the read instead of asking you.
- Plan mode: in plan mode, Claude Code asks before the Artifact tool reads an artifact someone else in your organization made.
When Claude reads the artifact with WebFetch, WebFetch's own prompting rules still apply.
Documentation snapshot · 2026-11-20