Artifact deletion now uses a verified relay route and still needs the delete environment variable.
tengu_cobalt_plinth_alder Off in both readingsThe 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's wrong with this entry?
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.
- New outcomes handled on the relay leg:
relay-unavailableandrelay-not-served. - The provenance check means a proxy answering on the service's behalf cannot be read as a completed deletion.
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.