kirodotdev
Using WSL2 Terminals but Kiro is confused and has executePwsh errors all the time
Before opening, please confirm:
- [x] I have searched for duplicate or closed issues
Operating System
Windows 11 (WSL2 Terminal environment)
Kiro Version
0.8.0
Bug Description
I use Kiro on Windows 11, but I do all my dev work in the WSL2 environment. This is all fine and works well (most of the time). I am continually having Kiro come back to me with:
I've been trying to use "executePwsh", but it's failed 7 times in a row. I'm clearly stuck in a loop.
What would you like me to do?
It feels like Kiro on Windows has a bias towards PowerShell, and it keeps getting into this state, which is very frustrating (it often happens multiple times in minutes).
I have a global steering file stating that Kiro should use wsl2 zsh terminal commands (this is the envirinment I operate in).
It would be nice for Kiro to detect the terminal setting in VSCOde config to understand the terminal and not insist that on Windows it needs to use PowerShell!
Steps to Reproduce
- Setup Kiro to use WSL2 shell
- Run spec driven tasks
- Kiro will eventually start failing with executePwsh confusion and be stuck in a loop.
I do not have more specific steps at this time.
Expected Behavior
It should read my steering files to start with, which would remove this annoyance!
Kiro should respect steering files at both the global and project levels (I find it doesn't always read them).
Conversation ID
96ad6f0c-6dad-4218-b02a-c79e0d713e2d
Additional Context
No response
