Allow Windows Codex App to use a custom shell executable, e.g. PowerShell 7 `pwsh.exe`

Codex
1

On Windows 10, I have PowerShell 7 installed, currently `pwsh.exe` 7.6.2.

However, when Codex App is configured to use “PowerShell” as the integrated terminal, it appears to use Windows PowerShell 5.1 via `powershell.exe` instead of PowerShell 7 via `pwsh.exe`.

This is problematic because PowerShell 5.1 and PowerShell 7 have different behavior, compatibility, modules, encoding defaults, and command support.

Current behavior

Codex App lets me choose a terminal type such as PowerShell, Command Prompt, Git Bash, or WSL.

But on Windows, choosing “PowerShell” does not let me specify whether Codex should use:

`C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe`

or:

`C:\Program Files\PowerShell\7\pwsh.exe`

Expected behavior

Codex App should allow users to configure the exact shell executable path and optional launch arguments.

For example:

Shell executable:

`C:\Program Files\PowerShell\7\pwsh.exe`

Arguments:

`-NoLogo -NoProfile`

Why this matters

PowerShell 7 is the current cross-platform PowerShell runtime, while Windows PowerShell 5.1 is legacy and Windows-only.

There’s a lot of developers are still using windows10.

2

Thanks for the clear example! We hear the request to choose the exact Windows shell executable and launch arguments, beyond selecting a terminal type. We appreciate the feedback and don't have a timeline to share.