{"version":"2.1.247","anchor":"artifact-delete-rewritten-around-session-relaying","canonical_anchor":"artifact-delete-rewritten-around-session-relaying","heading":"Artifact delete rewritten around session relaying","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-delete-rewritten-around-session-relaying","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact delete rewritten around session relaying\n\nArtifact deletes now go through a relay and report unverified responses as unconfirmed rather than deleted.\n\n**What**\n\nDeleting 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.\n\n**Details**\n\n- 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.\n- 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.\n- 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.\n- New telemetry reasons record why a delete ended as it did: `not_found_foreign`, `ok_foreign`, `relay_error`, and `ccr_credential_refused`.\n- When delete is unavailable, a dedicated message points you at claude.ai or the `\/artifacts` command instead.\n- The same session-kind check now also suppresses the `custom_ca` classification that TLS errors would otherwise be labelled with.\n- A `DELETE \/{slug}` Artifact route was added to the route table.\n\n**Evidence**\n\n`Deleting Artifacts isn't available in this cloud session right now, so nothing was deleted; do not retry here.`, `tengu_cobalt_plinth_alder`\n\n- Flag `tengu_cobalt_plinth_alder`: Off in both readings (read for one account on one subscription tier against v2.1.247; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}