Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.251 Home All releases ←olderv2.1.250

Claude Code v2.1.251 28 Aug 2026

Artifact creation can pre-arm its approval

You'll notice

Useful3 Signal3

Permissions

Approving artifact creation once can let a follow-up creation through without another prompt.

What

The permission decision for creating an artifact from an artifact type can now be marked as automatically approvable rather than a plain yes or no, letting a follow-up creation proceed without a fresh prompt when an internal arming check has already passed.

Details

the prompt text remains, asking to create a new private artifact on claude.ai from a named artifact type
which conditions set the arming state is decided inside the client and is not exposed as a setting

Evidence

Claude wants to create a new private artifact on claude.ai from the artifact type at

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.251 →