{"version":"2.1.221","anchor":"bash-sandbox-prompt-no-longer-promises-tmpdir-everywhere","canonical_anchor":"bash-sandbox-prompt-no-longer-promises-tmpdir-everywhere","heading":"Bash sandbox prompt no longer promises $TMPDIR everywhere","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/bash-sandbox-prompt-no-longer-promises-tmpdir-everywhere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Bash sandbox prompt no longer promises $TMPDIR everywhere\n\nClaude now makes its own scratch directory in sandboxed shells instead of assuming a temp variable exists.\n\n**What**\n\nThe sandbox section of the Bash tool description now only tells Claude to use `$TMPDIR` when the sandbox actually exports it, and otherwise tells it to create its own scratch directory.\n\n**Details**\n\n- the old \"always use the `$TMPDIR` environment variable\" text is kept when the helper returns true, meaning the platform is Windows or the sandbox profile is not \"relaxed\"\n- otherwise the model is told to make its own scratch dir with `mktemp -d`\n- so a relaxed non-Windows sandbox profile now gets the mktemp guidance\n\n**Evidence**\n\n`the sandbox does not export it in this configuration`\n\n- Area: Sandbox\n- Names: `$TMPDIR`, `mktemp -d`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}