Hello, I am writing this to address a very serious issue. When I use Codex, it works well, but after some time or when I use Codex on multiple files. It gets stuck in one of the files and will not accept my response. Thus, always asking for approval and the whole session gets paused.
Right now, I have to disable and restart the extension to solve this, but the issue persists. It’s getting very difficult to work this way, and I hope you solve it at your earliest convenience.
8 Likes
Check the GitHub OpenAI Codex issues
https://github.com/openai/codex/issues
There are many noted open issues found for stuck
https://github.com/openai/codex/issues?q=is%3Aissue%20state%3Aopen%20stuck%20label%3Abug
If you feel your issue is not a duplicate of one of the existing issues, either open or closed
https://github.com/openai/codex/issues?q=is%3Aissue%20stuck%20label%3Abug
consider opening a new issue.
I’m seeing the same behavior. On gpt-5.3-codex, the approval prompt blocks the Codex input UI, but the agent keeps executing commands in the background anyway. This locks me out of typing/submitting, so the session becomes unusable until I restart the extension.
Details:
Model: gpt-5.3-codex (this does not happen for me when I select gpt-5.2-codex in the model selector!)
Extension: openai.chatgpt 0.4.71 (published 2025‑08‑27, last released 2026‑02‑05)
IDEs: both Cursor and VS Code (latest), same behavior in both!
Symptom: approval dialog appears; command seems to run anyway; input box becomes unresponsive
It started as soon as Codex 5.3 was released a couple days ago, so it’s clear that that release caused this to start acting up.
2 Likes
@honeypercentage Welcome to the forum!
While you can note it here, the OpenAI devs do not check this forum as much as they check the issues.
The best thing to do is to find the exact issue you have that is not noted as a duplicate and leave a thumbs up or if you want to be more clear, leave a simple me too reply. The counts of such really do help to figure what gets prioritized.
Yeah I’ve been having this same problem too. The codex CLI seems to work, but the app does not. It’ll do a simple get-content and hang up on it until I restart vs code/cursor.
This is not a bug but a feature. Let me explain. When Codex asks for permission to run a command it waits for you to respond. One command requires exactly one Yes response to proceed. However, sometimes, there are multiple commands that Codex needs approval to run. It might not be obvious that there are more than one, but if you continue giving it approval, you will eventually get to the last one and then Codex will resume work. I hope this helps