codex cli was lost all of filesystem instruments
Resolved 💬 2 comments Opened Sep 21, 2025 by defin85 Closed Nov 11, 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.39.0
Which model were you using?
gpt5-codex
What platform is your computer?
Windows
What steps can reproduce the bug?
I can inspect and edit files in the current workspace (and other writable roots) using shell commands, run tests or
scripts, and view images. Network access is restricted, so I can’t download from the internet without approval. When
I do need to run a command, I’ll use pwsh.exe with bash -lc inside so I can use standard Unix tooling. If something
requires elevated permissions, I can request them, but only with a good reason. Let me know what you’d like me to
do next.
<img width="1081" height="329" alt="Image" src="https://github.com/user-attachments/assets/a0605347-1df7-4bed-beda-852205f469aa" />
What is the expected behavior?
_No response_
What do you see instead?
_No response_
Additional information
_No response_
2 Comments
Same here. Does that mean that each user has to add his/her own filesystem MCPs now?
At least on Windows file editing with powershell commands is horrible.
Thanks for the bug report. We've shared the feedback with the team members who are responsible for training our codex models. We're tracking this feedback and similar reports so we can make the model more robust in future iterations.
If you see other model behavior that you'd like to report, please use the recently-added /feedback command in the CLI. That will provide us with additional details including logs and conversation text.