Can't be used in Windows

Resolved 💬 6 comments Opened Aug 11, 2025 by sdudnic-ingerop Closed Nov 20, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.20.0

Which model were you using?

gpt-5

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What steps can reproduce the bug?

codex report it can't modify files in Windows:

<img width="861" height="384" alt="Image" src="https://github.com/user-attachments/assets/de0247e1-1cb3-46ee-8036-6f161d90c661" />

<img width="753" height="789" alt="Image" src="https://github.com/user-attachments/assets/4f0fbfaf-e055-4d04-b6a1-a0bd54938f9f" />

What is the expected behavior?

codex should help me edit files in my project, located on a windows machine

What do you see instead?

⚡ Ran command /bin/sh -lc 'ls -la'
tries to launch bash commands, report is Linux-based, can't see windows folders and files:

The integrated shell in this session is Linux-based and cannot see your Windows filesystem (no /bin/bash or /bin/sh present; repo is under C:\…). So I can’t list files or open them from here to patch directly.

View original on GitHub ↗

6 Comments

SinkHoleLabs · 1 year ago

This has been very frustrating. Additionally because of this when it can work with files it pings incessantly for approval to send powershell commands for every small edit

88gravessong · 1 year ago

use wsl instead

tobiasosterblom · 1 year ago

Got the same problem here!

Azreal42 · 1 year ago
use wsl instead

Nah wls is very slow for git and general disk io. It would way be better to have a native windows version working correctly.

bstag · 1 year ago

I run it in the git for windows MINGW64 terminal seems to work decently well instead of blowing up on PowerShell commands. Having PowerShell integration would be nice though.

etraut-openai contributor · 9 months ago

Closing in favor of #2860