codex - 💡(How to fix) Fix Add PowerShell 7 / pwsh as a Codex Desktop integrated terminal shell option

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

This would make the integrated terminal match modern Windows developer environments more closely and avoid requiring profile handoff workarounds that launch pwsh from Windows PowerShell 5.1.

Code Example

C:\Program Files\PowerShell\7\pwsh.exe
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

App, Windows Desktop

What feature would you like to see?

Please add PowerShell 7 / pwsh as an option under Settings > Integrated terminal shell on Windows.

Today, the dropdown shows options like:

  • PowerShell
  • Command Prompt
  • Git Bash
  • WSL

On Windows, the PowerShell option appears to launch Windows PowerShell 5.1 (powershell.exe) rather than modern PowerShell 7 (pwsh.exe). PowerShell 7 is commonly installed at:

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

It would be helpful if Codex Desktop offered either:

  • A dedicated PowerShell 7 / pwsh option, or
  • A Custom shell executable path setting where users can choose a shell such as C:\Program Files\PowerShell\7\pwsh.exe.

Additional information

Environment observed:

  • Codex Desktop for Windows
  • Codex app version: 26.513.40821
  • Installed PowerShell 7 path: C:\Program Files\PowerShell\7\pwsh.exe
  • Installed PowerShell 7 version: 7.6.1
  • Windows PowerShell currently reports major version 5.1

This would make the integrated terminal match modern Windows developer environments more closely and avoid requiring profile handoff workarounds that launch pwsh from Windows PowerShell 5.1.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Add PowerShell 7 / pwsh as a Codex Desktop integrated terminal shell option