{"version":"2.1.307","anchor":"claude-code-disable-artifact-env-var-dropped-from-the-artifa","canonical_anchor":"claude-code-disable-artifact-env-var-dropped-from-the-artifa","heading":"CLAUDE_CODE_DISABLE_ARTIFACT dropped from the Artifact tool's setting entry","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/claude-code-disable-artifact-env-var-dropped-from-the-artifa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### `CLAUDE_CODE_DISABLE_ARTIFACT` dropped from the Artifact tool's setting entry\n\nThe Artifact tool's setting entry no longer names `CLAUDE_CODE_DISABLE_ARTIFACT`, though the variable name still appears elsewhere in Claude Code\n\n**Unclear.** Whether setting `CLAUDE_CODE_DISABLE_ARTIFACT` still turns off the Artifact tool is not clear.\n\n**What**\n\nThe Artifact tool publishes session output as a private web page on claude.ai. Claude Code describes how it can be turned off in one setting entry. That entry still names the deprecated `disableArtifact` key. It no longer names the environment variable `CLAUDE_CODE_DISABLE_ARTIFACT`. The variable's name still appears in other places in Claude Code.\n\nSeparately, `CLAUDE_CODE_SPAWNED_BY_SERVER` was removed from a list of environment variables that includes `CLAUDE_CODE_PROCESS_WRAPPER`, `CLAUDE_CODE_PROFILE_QUERY` and `CLAUDE_CODE_TEAMMATE_COMMAND`. That name also still appears elsewhere.\n\n**Why**\n\nThe environment variable was a way to turn the Artifact tool off. It may now be read elsewhere or not at all. Turning it off with `enableArtifact` set to `false` in a settings file does not depend on it.\n\n- Area: Artifacts\n- Names: `disableArtifact`, `CLAUDE_CODE_DISABLE_ARTIFACT`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}