{"version":"2.1.208","anchor":"windows-sandbox-binshell-now-accepts-object-form-and-custom-","canonical_anchor":"windows-sandbox-binshell-now-accepts-object-form-and-custom-","heading":"Windows sandbox: binShell now accepts object form and custom srt-win path","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208\/e\/windows-sandbox-binshell-now-accepts-object-form-and-custom-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208","markdown":"### Windows sandbox: binShell now accepts object form and custom srt-win path\n\n**What**\n\nTwo improvements to the Windows sandbox configuration.\n\nFirst, `binShell` can now be specified as an object `{\"exe\": \"...\", \"args\": [...]}` instead of only as a string token. This allows passing absolute paths to shells with custom argument arrays. The object form is Windows-only and is rejected on macOS\/Linux.\n\nSecond, a new `windows.srtWin.path` setting allows pointing the sandbox at a custom `srt-win.exe` binary instead of the packaged one.\n\n**Details**\n\n- `binShell` string form: bare token (`cmd`, `powershell`, `pwsh`) or absolute path to `bash.exe`\/`sh.exe`\/`pwsh.exe`\/`powershell.exe`\n- `binShell` object form: `{\"exe\": \"<absolute path>\", \"args\": [\"...\"]}`\n- Error message updated: now accepts `pwsh.exe` and `powershell.exe` in addition to the previous `bash.exe`\/`sh.exe`\n- `windows.srtWin.path`: if set, the file must exist; remove the key to fall back to the packaged binary\n- CA cert path is now passed to sandbox commands, enabling custom CA trust in Windows sandbox mode\n\n**Evidence**\n\n`binShell` object form (search for `\"binShell object form is Windows-only\"`) and srtWin path (search for `\"windows.srtWin.path is set to\"`)"}