Kiro Product
CLI
Feature Description
On Windows, kiro-cli defaults to PowerShell for executing shell commands. Users who have Git Bash installed (which ships with Git for Windows and is common in developer environments) have no way to tell kiro-cli to use it instead.
Proposed Solution
Add a configuration option (e.g. in kiro-cli config or via an environment variable like KIRO_SHELL) that lets users specify the shell executable to use for command execution on Windows. For example:
KIRO_SHELL=C:\Program Files\Git\bin\bash.exe
or a config file entry equivalent.
Environment
OS: Windows 11
Git Bash installed (C:\Program Files\Git\bin\bash.exe)
kiro-cli shell execution currently works via PowerShell
Use Case
Git Bash provides a POSIX-compatible shell environment, and many development workflows rely on bash syntax, POSIX tools (grep, sed, awk, find, curl, etc.) and bash scripting. When kiro-cli defaults to PowerShell, agents must translate all commands to PowerShell syntax — which is error-prone and produces commands that don't match what developers would run themselves.
Additional Context
No response
Kiro Product
CLI
Feature Description
On Windows, kiro-cli defaults to PowerShell for executing shell commands. Users who have Git Bash installed (which ships with Git for Windows and is common in developer environments) have no way to tell kiro-cli to use it instead.
Proposed Solution
Add a configuration option (e.g. in kiro-cli config or via an environment variable like KIRO_SHELL) that lets users specify the shell executable to use for command execution on Windows. For example:
KIRO_SHELL=C:\Program Files\Git\bin\bash.exe
or a config file entry equivalent.
Environment
OS: Windows 11
Git Bash installed (C:\Program Files\Git\bin\bash.exe)
kiro-cli shell execution currently works via PowerShell
Use Case
Git Bash provides a POSIX-compatible shell environment, and many development workflows rely on bash syntax, POSIX tools (grep, sed, awk, find, curl, etc.) and bash scripting. When kiro-cli defaults to PowerShell, agents must translate all commands to PowerShell syntax — which is error-prone and produces commands that don't match what developers would run themselves.
Additional Context
No response