Claude Code Fixes Artifact Permissions: No Prompt for Your Own Artifacts, Stricter Checks for Public Ones
Claude CodeView original changelog
Claude Code 2.1.325 stops asking permission before Claude reads the user's own artifact or its data. It also tightens confirmation for artifacts that people outside the organization can see. Subagents and some publishes no longer skip the confirmation, and auto mode's yes now covers only one change.
Key Takeaways
- Reading your own artifact no longer prompts for permission.
- Subagents could change externally visible artifacts without asking in some cases, and no longer can.
- "Don't ask again" no longer lets some publishes skip the confirmation for such pages.
- Auto mode's approval now covers a single change to a public artifact.
- Deny and ask rules for the Artifact tool now apply in cloud sessions where they were missed.
- The fixes center on artifacts that people outside your organization can see.
Fewer prompts for your own artifacts
Claude no longer asks for permission before reading the user's own artifact or its data.
Stricter checks for externally visible artifacts
Several cases where a change to an artifact visible to people outside the organization could skip a confirmation are closed:
- Some subagents changed such an artifact, or uploaded files to it, without asking when an allow rule was set or uploads were approved earlier.
- Some publishes skipped the confirmation when "don't ask again" had been chosen for Artifact.
- Auto mode judged only the first change to such an artifact. Its yes now covers that change alone.
Deny and ask rules
Deny and ask permission rules and hooks for the Artifact tool did not apply in some cloud sessions. They now do.