Source Intelligence

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.236 Home All releases olderv2.1.235 v2.1.237newer
Claude Code v2.1.236

Specific reasons when an artifact write approval does not match the file

You'll notice
Useful3 Signal2
Artifacts

Failed artifact file approvals now name the reason and the fix instead of generic denial text.

What

When approving a file for an artifact fails, you now get a named reason and what to do about it instead of generic denial text.

Details
  • Reasons distinguish the file changing since approval, reaching the file through a symbolic link, a hard link, a read that would need permission, no identity, the path not being a regular file, and size.
  • Each carries remediation, such as passing the resolved path or copying the file under the working directory.
  • The symlink, hard-link and size checks now live in one shared helper rather than being repeated per action.
Evidence

file_path reaches its file through a symbolic link that resolves somewhere this session may not read without asking

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.236 →