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.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Failed artifact publish tells you a slug was already reserved

You'll notice
Useful2 Signal1
Artifacts

A failed artifact publish now tells you a name was already reserved, so you retry against it.

What

If a publish fails after reserving a name for the artifact, the result now tells you to retry against that reserved name rather than publishing fresh, instead of keeping the reserved value silently. Applies when the publish reserved a slug and none was supplied.

Evidence

A slug WAS reserved

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