{"version":"2.1.317","anchor":"new-env-vars-forwarded-to-spawned-processes-claude-code-dis","canonical_anchor":"new-env-vars-forwarded-to-spawned-processes-claude-code-dis","heading":"Two Claude Code environment variables now reach the programs it starts","tier":"internal","area":"Environment Variables","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-env-vars-forwarded-to-spawned-processes-claude-code-dis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Two Claude Code environment variables now reach the programs it starts\n\n`CLAUDE_CODE_DISABLE_MCP_TASKS` is now passed on to programs Claude Code starts, and `CLAUDE_CODE_HOST_SHORT_TEMP_DIRS` is always set for them\n\n**Unclear.** What `CLAUDE_CODE_DISABLE_MCP_TASKS` actually switches off is not stated.\n\n**What**\n\nAn environment variable is a named setting a program reads when it starts. When Claude Code starts another program, it builds that program's environment variables, and it now includes two more:\n\n- `CLAUDE_CODE_DISABLE_MCP_TASKS`: if it is set where Claude Code was started, it is passed on as `1`.\n\n- `CLAUDE_CODE_HOST_SHORT_TEMP_DIRS`: always set, to `1` or `0`, depending on a check of the machine Claude Code runs on.\n\nNeither name appeared in the previous build.\n\n**Why**\n\nIf you set `CLAUDE_CODE_DISABLE_MCP_TASKS`, it now carries through to the programs Claude Code starts. Those programs can also see whether short temporary folder paths apply on this machine.\n\n- Area: Environment Variables\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}