Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.247 ·

Artifact deletion goes through the relay and can refuse in cloud sessions

Artifact deletion now uses a verified relay route and still needs the delete environment variable.

Use it now Notable No documentation found In Development
JSON All of v2.1.247
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.247,
What probably matters to youSection of the release
What

Deleting an artifact no longer talks to the frame client directly; it uses a relay-only DELETE route that recognises when the relay is unavailable or not serving this session, verifies that 404s and success statuses really came from the Artifact service rather than an intercepting proxy, and shows a refusal message in cloud sessions that cannot delete. Delete itself still requires the CLAUDE_CODE_ARTIFACT_DELETE environment variable or the flag tengu_cobalt_plinth_alder, whose fallback is off.

Details
  • New outcomes handled on the relay leg: relay-unavailable and relay-not-served.
  • The provenance check means a proxy answering on the service's behalf cannot be read as a completed deletion.
Evidence

Deleting Artifacts isn't available in this cloud session right now

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

Read from
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: off

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 has happened since
Flag reading moved The flag server now returns on for tengu_cobalt_plinth_alder, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_cobalt_plinth_alder, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_cobalt_plinth_alder, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_cobalt_plinth_alder, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_cobalt_plinth_alder, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.247 →

Feedback