{"version":"2.1.317","anchor":"host-short-temp-dirs-env-var-set-from-entrypoint-handling","canonical_anchor":"host-short-temp-dirs-env-var-set-from-entrypoint-handling","heading":"Some launches now set CLAUDE_CODE_HOST_SHORT_TEMP_DIRS to 0 unless you set it","tier":"use","area":"Environment Variables","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/host-short-temp-dirs-env-var-set-from-entrypoint-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Some launches now set CLAUDE_CODE_HOST_SHORT_TEMP_DIRS to 0 unless you set it\n\nDepending on how Claude Code was launched, it clears CLAUDE_CODE_ENTRYPOINT and may set CLAUDE_CODE_HOST_SHORT_TEMP_DIRS to 0\n\n**Unclear.** It is not clear which launch types are affected or what CLAUDE_CODE_HOST_SHORT_TEMP_DIRS changes.\n\n**What**\n\nAn environment variable is a named setting passed to a program when it starts. Claude Code now checks `CLAUDE_CODE_ENTRYPOINT`, which records how it was launched:\n\n- For certain values, it removes `CLAUDE_CODE_ENTRYPOINT` from the environment.\n\n- For some of those, it also sets `CLAUDE_CODE_HOST_SHORT_TEMP_DIRS` to \"0\", unless you already set that variable yourself.\n\n**Why**\n\nThis changes how temporary folders are handled for some kinds of launch. Setting `CLAUDE_CODE_HOST_SHORT_TEMP_DIRS` yourself keeps your own value.\n\n- Area: Environment Variables\n- Names: `CLAUDE_CODE_HOST_SHORT_TEMP_DIRS`, `CLAUDE_CODE_ENTRYPOINT`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}