AI Agent Hub
Back to plugins
⚙️

dsh-win-bash-fix

Workflow Updated 2026.08.19

Run the following command in DeepSeek Harness:

dsh plugin install Jyleaves/dsh-win-bash-fix

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

Run dsh plugin install Jyleaves/dsh-win-bash-fix in your terminal to install; the full source is available at https://github.com/Jyleaves/dsh-win-bash-fix

About this plugin

On Windows, every bash tool call in DeepSeek Harness fails outright with a PTY startup crash, forcing the model into retry loops that flood the thinking chain with distressed let me phrases. The root cause is a stack of three platform-specific issues: an unimplemented win32 process inspector, missing MSYS environment variables, and a restricted-token file sandbox that is fundamentally incompatible with MSYS2 shared-memory mappings (Win32 error 5, ACCESS DENIED).

dsh-win-bash-fix resolves all three layers as a pure runtime patch (cordis plugin): it injects the correct MSYS environment for Git Bash, supplies a working win32 process inspector, and bypasses the restricted-token sandbox where it conflicts with MSYS2. It also ships two healthy thinking-chain presets, minimal-win and anchored-win, which use few-shot examples and a team framework to stabilise the chain toward we / let's collective voice. Because everything is a runtime hook, official dsh upgrades do not break the fix, and on non-Windows platforms the plugin simply no-ops.

Ideal for Windows developers who rely on the bash tool daily (reading files, running git, executing scripts) and want to eliminate the tool-error retry loop and restore a healthy thinking chain. Note: the plugin bypasses the Windows file sandbox, so uninstall it before running untrusted code to restore the official sandbox protection.

Use Cases

  • dsh bash tool crashes on every call with PTY startup error on Windows
  • Model stuck in retry loops with distressed let me spam due to persistent tool failures
  • Agent workflow requiring a stable English collective-thinking chain (we / let's)

Best For

  • Developers on Windows who rely on the dsh bash tool daily
  • Users seeking to eliminate tool-error loops and restore a healthy thinking chain
  • Windows dsh users who need the fix to persist across official upgrades