gemini-cli - 💡(How to fix) Fix run_shell_command that generalist uses forces use of inappropriate powershell.exe rather than pwsh.exe [1 comments, 2 participants]

What happened?

gemini-cli and its sub-agents (particularly generalist) should use (or at least allow) use of PowerShell 7 (first released in March, 2020).

Information from gemini-cli itself on the problem of the generalist sub-agent inability to do basic things: ✦ The choice of powershell.exe is not my own; it
is hardcoded into the built-in run_shell_command tool of the Gemini CLI application (v0.39.0). As a guest agent operating within this CLI, I do
not have the ability to modify the CLI's own
source code or its core execution engine to swap the legacy shell for pwsh.exe or llmbash.exe.

The "File not found" error persists because
every time I try to run a command—even when I
specify the absolute path to your modern
binaries—the CLI's underlying wrapper attempts
to invoke powershell.exe -NoProfile -Command,
which appears to be missing or blocked in your
environment.

Technical Conflict

• Gemini CLI Core: Hardcoded to use powershell.exe.
• Your Environment: Standardized on pwsh.exe and llmbash.exe.
• Result: I am currently "execution-locked" because my only path to the CPU is through a binary (powershell.exe) that does not exist on your system.

What did you expect to happen?

the modern Powershell v7 should be usable. Generalst cannot even execute an executable I built that provides GO for bash commands.

Client information

<details> About Gemini CLI │ │ │ │ CLI Version 0.39.0 │ │ Git Commit 398f78dca │ │ Model gemini-3-flash-preview │ │ Sandbox no sandbox │ │ OS win32 │ │ Auth Method Signed in with Google │ │ xxxx │ ) │ │ Tier Gemini Code Assist in Google One │ │ AI Pro │ │ GCP Project velocikey-rnd │ │ IDE Client Antigravity </details>

Login information

logging in with google account (auth)

Anything else we need to know?

This bug must be impacting many, many companiers.