{"version":"2.1.304","anchor":"sandbox-env-filter-has-an-extra-condition-for-env-var-names","canonical_anchor":"sandbox-env-filter-has-an-extra-condition-for-env-var-names","heading":"The sandbox has an extra rule for which environment variables get through","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/sandbox-env-filter-has-an-extra-condition-for-env-var-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### The sandbox has an extra rule for which environment variables get through\n\nThe filter deciding which environment variables reach sandboxed commands now has an extra condition\n\n**Unclear.** It is not clear which variable names the new condition matches, so which variables are now passed or held back is unknown.\n\n**What**\n\nEnvironment variables are named settings that a program passes on to the commands it runs. When Claude Code runs a command in the sandbox, which is a restricted space with limited access to your system, it filters which of these variables get through. That filter already had rules for `TMPDIR`, `TMP` and `TEMP` and for a set of allowed names. It now has one more condition.\n\n**Why**\n\nThis changes which environment variables reach commands run in the sandbox.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}