{"version":"2.1.299","anchor":"windows-sandboxed-shell-settingsenv-vars-passed-on-command","canonical_anchor":"windows-sandboxed-shell-settingsenv-vars-passed-on-command","heading":"Windows sandboxed commands now receive environment variables from settings","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/windows-sandboxed-shell-settingsenv-vars-passed-on-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Windows sandboxed commands now receive environment variables from settings\n\nOn Windows, environment variables from settings or `\/env` now reach sandboxed commands, and ones that cannot be passed are logged as left out\n\n**Unclear.** Which variables cannot be passed into the sandbox is not stated.\n\n**What**\n\nOn Windows, commands run inside the sandbox (a walled-off space that limits what a command can reach) now receive the environment variables you set in your settings or with `\/env`. Environment variables are named values a program reads when it starts. Any that cannot be passed are logged with the message \"these variables from settings or \/env are not passed to the sandboxed command\".\n\nIf setting up the sandbox for a command is cancelled, the command now stops before it starts, and Claude Code logs `tengu_shell_abort_before_spawn`.\n\n**Why**\n\nIf you use the sandbox on Windows, variables from your settings may now reach your sandboxed commands where they did not before, and some may still be left out. Check the log if a command is missing one.\n\n- Area: Sandbox\n- Names: `\/env`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}