The Codex plugin in VSCode is regularly stuck in the loading screen. Having to try and bugfix this every day takes away 30 minutes at least when codex was supposed to save time. Might have to consider another coding agent if this keeps up.
Yes, I’ve seen this personally myself on numerous occasions. The part that makes it frustrating at least to me is there’s absolutely zero indications of what’s happening. There really does need to be some sort of debug output without having to crawl through the Codex client logs. I’m not sure why the VSCode extension is so bad. In the past I just had to start a new conversation because that was the only thing that worked.
Agree. Claude code works on VS Code remote ssh meanwhile Codex gets stuck at this loading screen and unresponsive window error.. which stifles time.. tried uninstall/reinstall reload window nothing has worked as of this past week. Almost seems like Microsoft/Anthropic is blocking the app from functioning in VS code.
Increase the memory allocation in the VS Code settings. I had the same issue; I allocated 16 GB, and everything started working fine.
How do you do that? I’m not really seeing anything for memory other than JS/TS settings and scrollback.
It worked for me! Thank you so much.
In the vscode preferences > settings, you search for "JS/TS › Tsserver: Max Memory" and you increase the value
This should really be better communicated …
Also when setting values about 4096MB the path to a node executable (e.g. /usr/bin/node) is required for setting ts.tsserver.node.path
Hey @all! Getting stuck on the loading screen repeatedly definitely isn’t the experience you should have to troubleshoot every day.
For anyone on Windows, one official troubleshooting step is to run: codex doctor
from the Codex CLI. It checks for startup, connectivity, and performance issues that can affect Codex.
OpenAI’s Codex guidance also confirms the IDE extension is supported in VS Code and most VS Code forks.
The Tsserver Max Memory change mentioned above has helped some people in this thread, so its worth trying.
If you’re still seeing the issue after trying the steps above, please reach out to OpenAI Support with your environment details and any diagnostic output so it can be investigated further. View Codex Help Center. I’m going to close this thread now.
-Davinder