Hey, thanks for the report.
This is a known limitation in how the agent detects and picks shells. The detectShellType() function has explicit branches only for zsh, bash, and PowerShell. Everything else (nushell, fish, etc.) falls back to the system default, which on Windows always ends up being PowerShell.
I see you also created a related issue for the CLI here. It makes sense to track these separately since the input paths are different.
I’ve shared both reports with the team. The root cause analysis and the proposed fix with a general ShellType.Naive option are exactly the level of detail that helps with prioritization. No timeline yet, but your reports help raise visibility.
I’ll post an update here if there are any news.