{"version":"2.1.228","anchor":"artifact-is-disabled-by-its-own-switch-not-the-workflows-one","canonical_anchor":"artifact-is-disabled-by-its-own-switch-not-the-workflows-one","heading":"Artifact is disabled by its own switch, not the Workflows one","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/artifact-is-disabled-by-its-own-switch-not-the-workflows-one","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Artifact is disabled by its own switch, not the Workflows one\n\nTurning off artifacts now uses the artifact switch, not the Workflows one.\n\n**What**\n\nTurning off artifacts now honours `CLAUDE_CODE_DISABLE_ARTIFACT` and the `disableArtifact` setting, which is what the settings schema documented. The check previously read the Workflows environment variable and setting instead.\n\n**Details**\n\n- If you disabled Workflows in order to suppress artifacts, artifacts are switched back on; set `disableArtifact` or the environment variable instead.\n\n**Usage**\n\n`export CLAUDE_CODE_DISABLE_ARTIFACT=1` **Evidence** `disableArtifact`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_DISABLE_ARTIFACT`, `disableArtifact`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}