Codex Extension will not / almost never completes a single prompt on new update

Resolved 💬 4 comments Opened Nov 14, 2025 by kiptaylor Closed Jan 28, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.5.41

What subscription do you have?

Pro

Which model were you using?

Gpt Codex Low - high 5.1

What platform is your computer?

WIndows, using wsl for extensiuon

What issue are you seeing?

Lack of ability yo even do one task. It will think for upwards of hours and not complete the task at all or even do anything. Requires me to reload many times or even downgrade back to before 5.1 release. A problem, that took 40 seconds on the old release 0.5.39 , but when upgraded to any of the 5.1 versions that came out it will think for hours and not work. no error nothing.

What steps can reproduce the bug?

To replicate i just had to use latest version and do any task that uses your codebase. I.e. code, add folder xyz

What is the expected behavior?

It will think for ages or go through some steps but not complete, but on the 1% chance it completes it wont even do the task.

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 9 months ago

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

#6496
#6623
#6173
#6279
#6411

Powered by Codex Action

kiptaylor · 9 months ago

This is not a duplicate issue.

Disane · 9 months ago

I think this might be the same problem that I ran into, GPT5-Codex is unable to create or modify any files in WSL 2 (Ubuntu):

...
The earlier “Permission denied” came from the filesystem itself not allowing new files to be created at all (regardless of chmod/chown). If you still hit errors creating another file, it’s likely due to the workspace being mounted read-only (or OneDrive/WSL restrictions), not Unix permissions. For content changes like the report, editing via VS Code works even with the current mode.
...

Me:
could you try and create a file? see if this is working now?

Codex:  Still no luck—touch fails with “Permission denied,” so the underlying filesystem is preventing file creation despite the ownership change. That’s why I can’t add new files. We’ll have to keep using the workaround (you create files via your editor) until the environment is fixed. Let me know what you’d like me to work on next with that constraint in mind.

chmod won’t help here—the directory already shows drwxrwxrwx, so Unix permissions are wide open. The “Permission denied” is coming from the underlying filesystem (likely how the repo is mounted in this environment), not from mode bits.
...
won’t let us touch a file. Until the mount policy changes, the only reliable approach is what you’ve been doing: create/edit files via your own editor/WSL session, rather than through my tooling. Let me know when you need new content and I’ll provide it for you to paste in.

etraut-openai contributor · 7 months ago

Closing stale bug. If you're still seeing this behavior with the latest version of the extension, please use the /feedback command and open a new bug report.