Claude Code 2.1.327 changes artifact approval rules for managed organizations
The release refuses some new artifacts in sessions with nobody to approve them and stops the Artifact tool when Artifacts are turned off.
Claude Code 2.1.327, whose changelog is dated November 17, 2026, changes how artifacts are approved in organizations that require approval for each new artifact. In a session where nobody is available to answer, a new artifact is now refused at once, with no permission prompt. The changelog also says an artifact that only a plugin created or allowed can be refused. In practice, an unattended session ends the request rather than waiting on a prompt. The changelog doesn't say how an organization turns on per-artifact approval, or how a plugin's allowance is recorded.
The release also changes what happens when settings turn Artifacts off. The Artifact tool now refuses calls once that setting is off, including in sessions that were already running. The changelog doesn't say whether a session refused this way will report the reason to the user.
The publish prompt also loses its "don't ask again" option in several contexts: subagents, and turns that follow a background task result, a message from someone else, or a compaction. The changelog lists the contexts but gives no reason for the change.
The release includes several fixes to the approval path. Publishes had been failing with "the source file changed between approval and publish" when a synced or remote-backed folder had only changed a file's timestamp. A new artifact that had been approved was refused in a cloud scheduled task's session. Another was refused after an app built on the Agent SDK approved it, in organizations that require approval of each new artifact. The /artifacts list could also show only part of the list, or say "No artifacts yet", when a request for more of the list failed. It now retries and warns if it still can't load everything.
Other Artifact tool changes are listed as improvements. The tool can now read an uploaded file by the address shown on the artifact's page. Other address forms still fail, and most of those failures carry a message telling the caller to read uploads one per call, by id. On some calls, the tool now ignores the prompt, limit and label parameters it doesn't use, instead of failing the call.
What changed
Claude Code 2.1.327 refuses new artifacts at once in sessions where nobody can answer an approval prompt, and the Artifact tool now refuses calls once the Artifacts setting is off, including in already-running sessions.
Type: Breaking change · Applies to: Claude Code 2.1.327, Artifact tool
Why it matters
Organizations that require approval for each artifact may see refusals in background and cloud sessions. Logs now hold less detail on elicitation and hook answers, which affects audit trails.
What you can do
Check artifact approval policies and any background or cloud workflows that create artifacts, and confirm that audit processes still capture what they need.
Original source
Where we saw it
Claude Code changelog
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works