Windows PowerShell folder path issue
Resolved 💬 5 comments Opened Aug 25, 2025 by Antony-Jia Closed Dec 23, 2025
💡 Likely answer: A maintainer (seratch, member)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.23.0
Which model were you using?
default model
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What steps can reproduce the bug?
Just like code path “ D:\Code\starspirit-cli-dr\research-frontend-admin”， when i start codex i met
···
🖐 unexpected status 404 Not Found: {"code":5,"error":"url.not_found","message":"没找到对
象","method":"POST","scode":"0x5","status":false,"ua":"codex_cli_rs/0.23.0 (Windows 10.0.19045; x86_64)","url":"/v1/
responses"}
···
and if in the path like "D:\Code\starspiritclidr\researchfrontendadmin"
I think it caused by "-".
What is the expected behavior?
In complex path the codex is working fine.
What do you see instead?
_No response_
Additional information
_No response_
5 Comments
The 404 Not Found error might be due to your endpoint settings, not the file path resolution. I checked codex cli behavior with Windows OS + PowerShell, and it managed to resolve any type of file paths.
Thanks for the reply, I'll check it out.
I found the reason because there is .env file in this folder. I rename it and it works well. Is it problem?
@seratch , The Codex document state there is no support for Windows + PoweShell unless using WSL. How did you manage to run it?
This bug report is very old and likely stale. Closing.