Still unusable for daily work on 💙 Windows
What version of Codex is running?
codex-cli 0.25.0
Which model were you using?
gpt-5
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What steps can reproduce the bug?
Codex CLI is still unusable for me on Windows, even though the model is excellent. I hoped it would be fixed in version 0.25.0, but unfortunately it was not.
Here are the problems:
- Pasting images into the command line does not work
- The apply_patch safety gate cannot be disabled, every file change asks for confirmation
- Copying Windows paths does not work, backslashes get stripped
Without fixes for these three, I cannot use Codex on Windows in a professional setting. Please assign a higher priority to this.
<img width="995" height="544" alt="Image" src="https://github.com/user-attachments/assets/87e8d65b-b302-4fa9-aadd-cb1af87301b7" />
<img width="869" height="514" alt="Image" src="https://github.com/user-attachments/assets/ec9c94db-8537-4760-9ec3-e635e0edf753" />
<img width="841" height="531" alt="Image" src="https://github.com/user-attachments/assets/0abec7f1-7001-4430-8e4d-eef108b28e0e" />
What is the expected behavior?
_No response_
What do you see instead?
_No response_
Additional information
_No response_
6 Comments
Yea windows version has never worked imo use WSL and run it through linux.
Images dont work but the rest of it works solid
I tried installing the IDE extension, and it fixes the path issue and also allows pasting images (the model really reads them, tested).
However, the safety gate still cannot be disabled. So this is a temporary workaround for 2/3 problems.
<img width="1006" height="818" alt="Image" src="https://github.com/user-attachments/assets/80ad76b1-2c1c-472e-b6b2-9beffc6aae04" />
@jamneutrino
Sure, WSL is an option, but it is not native support. It is a workaround in a sandboxed Linux environment. I also run into many issues there with MCP servers that I run locally. For example, Playwright MCP does not work properly with the Chromium browser in WSL, etc. That is why native support needs to be improved.
How do you get the codex extension to even see your repo?
im getting:
I tried to scan the repo, but shell access isn’t available in this session, so I can’t read the files to identify it yet.
If you paste the top-level file list (and any README), I can tell you exactly what this project is. Quick ways to gather that:
PowerShell (top-level): Get-ChildItem -Force
PowerShell (key manifests): Get-ChildItem -Recurse -File -Name | Select-String -Pattern 'README|package.json|pnpm-lock|yarn.lock|pyproject.toml|poetry.lock|requirements.txt|Pipfile|go.mod|Cargo.toml|Gemfile|composer.json|Dockerfile|Makefile|vite.config|next.config|angular.json|astro.config|nuxt.config|gatsby-config|svelte.config'
Show contents if present: type README*, type package.json, type pyproject.toml, etc.
What I’ll look for:
package manifests (e.g., package.json, pyproject.toml, go.mod) to detect language/framework
framework markers (e.g., next.config.mjs, vite.config.ts, astro.config.mjs)
build/deploy files (Dockerfile, Makefile, CI configs)
app structure (e.g., src/, pages/, public/, templates/)
Share that output (or the README), and I’ll summarize the project clearly.
@marektomas-cz Windows is not my primary OS, but I am invested in making Codex work well on Windows, so to help me understand:
cmd.exeyour primary shell (as opposed to PowerShell)@bolinfest
_// I am not sure I fully understand the other questions or how they relate. Git for Windows is installed._
The problem is in "codex-rs/apply-patch/src/lib.rs". The check looks for
apply_patchat index 0, but in a Windows shell index 0 ispwsh, so the check never passes.pwshis there because of the bridge defined in "codex-rs/core/src/shell.rs".So I think the fix is to update "codex-rs/apply-patch/src/lib.rs" so it does not only look for
apply_patchat index 0, but instead walks the AST and finds theapply_patchcall even when it is inside the shell.If you need any other details, let me know.
Those should be fixed.