dsh-gitbash-preset (liceses/dsh-gitbash-preset)
Searching Database…
What is this?
A DeepSeek Harness (DSH) plugin that installs an alternate 'Minimal Mode (Git Bash)' agent preset, remapping DSH's built-in minimal-mode bash tool calls to Git for Windows' bash (MSYS) so minimal mode actually works on Windows.
How do I install this plugin?
Merge the plugin's cordis.patch.yml into your DSH profile patch layer and restart DSH; it auto-installs the bundled preset to ~/.dsh/.agent-presets/minimal-gitbash/ unless one already exists. You can skip the plugin entirely and just copy the agent-presets/minimal-gitbash/ folder there yourself.
Do I need Git for Windows installed?
Yes — the plugin needs a real bash.exe to map to, and it auto-detects one via the GITBASH env var, common Git install directories (ProgramFiles, ProgramFiles(x86), LOCALAPPDATA), or PATH.
Any big caveats before I rely on this?
Git Bash's MSYS runtime can't launch inside Windows' restricted-token sandbox, so bash only runs under DSH's 'danger-full-access' policy (or a one-time escalation); and unlike the original persistent PTY session, every bash call here starts a fresh shell, so cd and export don't carry over between commands.
Does this work on macOS or Linux too?
No, it's a Windows-only fix: macOS and Linux already have a usable bash for DSH's minimal mode, so this preset targets the Windows/Git-Bash gap specifically.
Why doesn't DSH's built-in minimal mode just work on Windows?
It relies on a PTY backend for persistent bash sessions, which DSH's subprocess layer rejects outright on win32, and even bypassing that, it hardcodes looking for 'bash' on PATH, which Windows doesn't have by default.
What happens if my session sandbox isn't full access?
The bash tool fails on the first call and shows guidance to either switch the session to full access or request a one-time sandboxed escalation with a justification, following DSH's normal approval flow.
Can I point it at a specific Git Bash install instead of auto-detecting?
Yes, set the shellPath field in the preset's gitbash-executor config (e.g. 'C:\Program Files\Git\bin\bash.exe') to skip auto-detection.
Will reinstalling the plugin overwrite my custom preset tweaks?
No, by default the installer skips copying if the preset already exists; only setting force: true makes it overwrite with the packaged files.
What are similar projects?
dsh-router-standard, dsh-agent-team-gui, oh-dsh, dsh-context, Blue-Whale-Harness, dsh-pocket, clearai-dsh, dsh-popout-sidebar
Which topics is it in?
deepseek-harness-plugin, dsh-plugins, cordis, bash, dsh, harness, dsh-plugin, sandbox, deepseek-harness, agents, plugin, tool