openclaw - 💡(How to fix) Fix Feature Request: Add tools.exec.shell config to specify default shell executable [1 participants]

Feature Request: tools.exec.shell configuration option

Is your feature request related to a problem? Please describe. On Windows, the exec tool defaults to PowerShell/cmd. Users who prefer bash (e.g., Git Bash from MSYS2, Cygwin, or Fork git's bundled bash) have no way to change this default behavior globally.

Describe the solution you'd like Add a tools.exec.shell configuration field (e.g., C:\\path\\to\\bash.exe on Windows, or just bash on Unix) that controls which shell the exec tool uses to interpret commands. On Windows, instead of launching cmd.exe or powershell.exe, OpenClaw would launch the configured shell executable directly.

Describe alternatives you've considered The current workaround is to manually wrap every command in a bash invocation (e.g., cmd /c "bash.exe -c \"...\""), but this:

• Requires manual escaping for every call
• Is error-prone with complex commands
• Doesn't scale — there's no way to make it the default behavior

A per-agent or global tools.exec.shell field in openclaw.json would solve this cleanly.

Additional context Schema path would be: tools.exec.shell (string, optional)

Example configuration:

{
  "tools": {
    "exec": {
      "shell": "C:\\Users\\Pheobe\\AppData\\Local\\Fork\\gitInstance\\2.50.1\\bin\\bash.exe"
    }
  }
}

This would allow Windows users with Git Bash (or other shells) to use their preferred shell consistently across all exec calls without manual wrapping.