athif23/dsh-shell-select

Picks which shell DSH runs agent commands in — PowerShell, cmd, Git Bash, WSL, bash, zsh or fish — from one settings card.

Decides, once per deployment, which shell every agent command runs in — PowerShell, Windows PowerShell, cmd.exe, Git Bash, WSL Bash, bash, zsh, fish or the system sh. The selection becomes ctx.shell, so it is not just the shell tool that follows it: hook commands and the harness's own probes do too, and the shipped bash and pwsh tools are denied with a reason naming shell. The choice belongs to the deployment rather than to the model — an agent gets a single shell tool and cannot pick a different shell per command — and a shell the current permission mode cannot confine is refused rather than escaped. Discovery runs by name through the harness's own executable resolution, with an executable override for a shell in an unusual location or a machine with two installs; an unresolvable path, or one naming a different shell, is an error rather than a cue to search. Each shell carries its own syntax notes into the model's instructions, so the agent is told what the selected shell needs.

Development & Runtime ★ 0 updated 2026-09-18
View on GitHub ↗

Install

dsh plugin --profile web add dsh-shell-select

The npm line. The choice is stored in the DSH settings document under shell-select and edited from Settings → Plugins → Shell selection with Save, Discard and Test. One subtlety the README documents because it would otherwise look like a bug: Test runs the saved selection, not the edits staged in the card, so save first if you want to test what you just typed.

Compatibility

Windows is the primary platform, and the README is precise about what that means for confinement: on Windows, Git Bash and WSL Bash cannot start under workspace-write and read-only permission modes — including for the card's own version probe — and run only under danger-full-access. That refusal is deliberate, since the alternative is running a shell the sandbox cannot confine. pwsh (PowerShell 7) is supported but was skipped on the author's test host only because it is not installed there, which is stated as the reason rather than presented as untested support. The selector runs inside the harness's existing sandbox, so deadlines and output limits still apply.

Details

Alternatives

tancheng33/dsh-spill-s3 · stuarthu/dsh-hot-reload · jkt-check/dsh-secret-scrub

More plugins in Development & Runtime

Browse more in Development & Runtime

Guides for Development & Runtime plugins