{"version":"2.1.307","anchor":"bash-env-builder-handles-node-use-env-proxy","canonical_anchor":"bash-env-builder-handles-node-use-env-proxy","heading":"Sandboxed shell commands now see NODE_USE_ENV_PROXY","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/bash-env-builder-handles-node-use-env-proxy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Sandboxed shell commands now see `NODE_USE_ENV_PROXY`\n\nIn the sandbox, `NODE_USE_ENV_PROXY` is no longer hidden, and proxy variables are added unless it is set to something other than `1`\n\n**What**\n\nClaude Code can run shell commands inside a sandbox, a restricted environment that limits what a command can reach. It builds the set of environment variables (named settings passed to every program) that those commands see. `NODE_USE_ENV_PROXY` is no longer hidden from sandboxed commands.\n\nClaude Code also adds its proxy variables to that environment unless `NODE_USE_ENV_PROXY` is set to a value other than `1`.\n\n**Why**\n\nThis affects how network proxies behave in sandboxed or remote shells. If you set `NODE_USE_ENV_PROXY` to anything other than `1`, the proxy variables are not added.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}