Windows: use Cygwin bash, not Powershell

Resolved 💬 4 comments Opened Jan 23, 2026 by alainfrisch Closed Mar 7, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

I start Codex from a Cygwin bash, and I'd like it to use that shell, not Powershell. This will in particular allow sharing permission rules with those used under WSL.

Btw, currently the rules are all like:

prefix_rule(pattern=["C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe", "-Command", "FULL COMMAND"], decision="allow")

which is pretty useless (the full command is just the 2nd argument to powershell -> no way to specify a useful "prefix" of the argument list)

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 7 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #9581

Powered by Codex Action

alainfrisch · 7 months ago

My request is indeed related to #9581, but I'm not so much interested to choose between powershell and cmd, rather use bash from cygwin.

etraut-openai contributor · 5 months ago

This feature request hasn't received enough upvotes, so I'm closing it.

GitMurf · 5 months ago

I know this is closed, but also wondering why Codex is using the old PowerShell v5.1 and not pwsh 7+?