{"version":"2.1.281","anchor":"commands-that-reference-tmpdir-get-a-claude-temp-dir-on-wind","canonical_anchor":"commands-that-reference-tmpdir-get-a-claude-temp-dir-on-wind","heading":"Commands that reference TMPDIR get a Claude temp dir on Windows too","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/commands-that-reference-tmpdir-get-a-claude-temp-dir-on-wind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Commands that reference TMPDIR get a Claude temp dir on Windows too\n\nOn Windows, shell commands that mention TMPDIR now get their own Claude temp directory, as they already did with sandboxing on\n\n**What**\n\n`TMPDIR` is the environment variable that tells programs where to put temporary files. When a shell command mentions it, Claude Code sets up a separate temporary directory for that command. Before, this happened only when sandboxing was on. Sandboxing is Claude Code's feature for limiting what commands can touch. It now also happens on Windows.\n\n**Why**\n\nOn Windows, commands that rely on `TMPDIR` now get a temporary folder set up for them, even without sandboxing.\n\n- Area: Windows\n- Names: `TMPDIR`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}