AI Agent Hub
Back to plugins
🖥️

dsh-gitbash

Client Updated 2026.09.14

Run the following command in DeepSeek Harness:

dsh plugin install yunuo110/dsh-gitbash

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install yunuo110/dsh-gitbash in your DeepSeek Harness terminal; the source repository is at https://github.com/yunuo110/dsh-gitbash .

About this plugin

When running DeepSeek Harness on Windows, the shell tool the model sees defaults to pwsh. In practice, models are far more fluent in POSIX/bash syntax than in PowerShell, so commands occasionally leak $env:VAR references or bare backslash paths that need constant correction. dsh-gitbash solves exactly this one problem: it adds no new modes and registers no new tools. It simply swaps the backend of the existing bash tool to Git for Windows Bash, hides pwsh from the prompt, and rejects any stale pwsh calls at the guard layer. The tool name, invocation signature, workdir, and timeout parameters all stay identical; the only change is that the description text is rewritten with MSYS2/bash conventions and commands actually run through bash.exe -lc.

At startup the plugin auto-detects the Git Bash path via environment variables, Program Files, Scoop, or PATH (with Windows System32 excluded). You can pin shellPath or tune timeouts and output limits in cordis.patch.yml. Every invocation is a fresh non-interactive shell with no persisted cd, export, or alias state, matching sandbox expectations. On non-Windows systems the plugin is a complete no-op, so it is safe to install in any DSH profile without conditional logic.

It fits a specific workflow: your primary dev machine is Windows with Git for Windows, and you routinely ask the model to run git status, npm test, or make inside DSH. You want stable POSIX output without repeated corrections. There is no workflow change, no extra token cost, and no new tool surface. It is a silent, zero-perception backend fix that takes effect the moment you restart DSH.

Use Cases

  • Running git status, npm test, or make via DSH on Windows with stable POSIX syntax
  • Eliminating PowerShell syntax leaks like $env:VAR or bare backslashes in model-generated commands
  • Keeping a single bash tool surface across Windows and non-Windows DSH profiles without conditional logic

Best For

  • DSH users whose primary dev machine is Windows with Git for Windows
  • Developers who want stable POSIX/bash output from the model without repeated corrections
  • Small teams standardizing DSH shell tool behavior across Windows and non-Windows environments