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.247 Home All releases olderv2.1.246 v2.1.248newer
Claude Code v2.1.247

Artifact delete rewritten around session relaying

You'll notice
Useful3 Signal3
Artifacts

Artifact deletes now go through a relay and report unverified responses as unconfirmed rather than deleted.

Feature flag
tengu_cobalt_plinth_alder Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.247: on

Read once, for one account on one subscription tier, against v2.1.247. It isn't a statement about your account. What a flag value here can and cannot tell you

What

Deleting an Artifact no longer posts directly to the service. In a hosted cloud session the delete is routed through a relay, and in a bot context it is refused outright, where before any remote session refused it. The code also now verifies that the response genuinely came from the Artifact service, so an unverified success is reported as unconfirmed rather than as a deletion.

Details
  • Deletion stays off unless the environment variable CLAUDE_CODE_ARTIFACT_DELETE is set, or the server turns on the flag tengu_cobalt_plinth_alder, whose built-in fallback value is off.
  • Refusal used to trigger on the environment variable CLAUDE_CODE_REMOTE alone; it now also requires a new check of what kind of session is running, so ordinary remote sessions can delete through the relay.
  • A 404, or a 204 success that is not vouched for as coming from the Artifact service, produces a "couldn't confirm" result instead of reporting the Artifact as deleted.
  • New telemetry reasons record why a delete ended as it did: not_found_foreign, ok_foreign, relay_error, and ccr_credential_refused.
  • When delete is unavailable, a dedicated message points you at claude.ai or the /artifacts command instead.
  • The same session-kind check now also suppresses the custom_ca classification that TLS errors would otherwise be labelled with.
  • A DELETE /{slug} Artifact route was added to the route table.
Evidence

Deleting Artifacts isn't available in this cloud session right now, so nothing was deleted; do not retry here., tengu_cobalt_plinth_alder

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