Codex Extension on VS code has not been working (there was a new udpate for 5.1). Cloud seems to be working fine, but the VS Code extension chats perpetually stall. Is anyone else having this issue?
2 Likes
Same issue for me. been doing this for the past 10-20 minutes, I think.
same/same been like that for almost 2 hours on my end
Codex in VSCode is now completely unusable. Prompts spin and do not complete.
1 Like
Same here. It is not responding at all.
1 Like
Same here. Just says Thinking… I tried reinstalling the extension, restarting my system and still broke. Please fix.
Simple: Just check the staus as @aprendendo.next did.
If I encounter problems like this, I always check the status page first…
Same problem. Constantly thinking, regardless of mode, model, and effort. Tried reinstalling, rolling back version. Issue arose ~2PM ET.
this post was created before the status page was updated 
the status page’s timestamp was updated to include the earliest report of the issue!
I’m talking to those that have posted AFTER the status page was updated.
seems like it up for me.
Sry, only GPT-5.1 model, not codex-max and it works bad.
Same issue for me. Thought I was going crazy.
I pinned to the 0.544 release(gpt -5-codex) and it seems to be working much better - 5.1 is not my favorite
Seems like the issue was fixed for about a half hour, but is starting to bug out again. I’m back to “Thinking” for over 5 minutes now. Sheesh. 
1 Like
This problem is back again, and it’s 9:00pm on a Sat night and I have to throw the towel in for the night. We have to start figuring out our own redundancy, this is a serious problem for the level of dependency on these systems.
1 Like
It’s back . . . . . it’s codex and open ai browser too, very glitchy.
1 Like
I am having huge issues with VS Code Codex today.
sooo glitchy not even responding any more
Hello guys, I had the same issue (Codex stuck loading while editing code) for days. In the VS Code output, I found this error :
2025-11-26 13:45:25.846 [error] Unknown MCP notification: codex/event/warning {“id”:“0”,“msg”:{“type”:“warning”,“message”:“Repository snapshot encountered large untracked directories: projects/Data/projects/Data/uniprot_cache_string (46590 files), projects/Data/projects/Data/mobidb_cache_string (20447 files), 3 more. This can slow Codex; consider adding these paths to .gitignore or disabling undo in your config.”},“conversationId”:“019abfd9-b8d1-7063-babc-1736fe2b5ac3”}
I fixed it by adding those folders to a .gitignore. Since then, Codex works normally again.
Not sure it’s the same root cause for you, but sharing in case it helps.
1 Like