VS Code Codex extension stuck on “Loading…” forever (Windows 11)

Resolved 💬 13 comments Opened Nov 21, 2025 by SvenBudak Closed Nov 22, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

vscode Plugin (not CLI based)

What subscription do you have?

Plus Plan

Which model were you using?

codex

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Codex VS Code extension gets stuck in an infinite loading state.
The sidebar shows “Loading Codex…” forever and never becomes usable.

There are no error messages.
Even after several minutes nothing appears — no login prompt, no model selector, nothing.

Tried so far:

  • Reinstalling the Codex extension
  • Updating to the newest VS Code version
  • Restarting VS Code and Windows
  • Removing the extension folder manually
  • Clearing VS Code extension cache

None of this helped — the extension still never loads.

What steps can reproduce the bug?

  1. Install the Codex VS Code extension
  2. Open the “Codex” sidebar
  3. It stays on “Loading…” forever
  4. No interactions are possible, and no error output appears

This happens 100% of the time.

What is the expected behavior?

The extension should load normally, show the chat UI, allow model selection, and function without getting stuck.

Additional information

Additional information

  • I’m on the newest Windows 11 build
  • VS Code is fully updated
  • Codex extension version is the latest from the marketplace
  • The CLI works fine, only the VS Code plugin is broken
  • No VPN or proxy is used

If logs are needed, please let me know where to find them — the extension currently doesn’t show any.

View original on GitHub ↗

13 Comments

github-actions[bot] contributor · 8 months ago

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

  • #6297
  • #6192

Powered by Codex Action

etraut-openai contributor · 8 months ago

Do you have MCP servers configured? Do you have any other non-default configuration settings in config.toml?

SvenBudak · 8 months ago

I’m not using any MCP servers, and I haven’t configured anything manually.

My config.toml is basically empty — I only opened it once to look at it, but I didn’t add anything. Everything is running with default settings.

Also relevant: I’m using WSL on Windows 11.

grahama1970 · 8 months ago

I'm getting the same problem (as of this morning) on Ubuntu. The terminal codex works fine. Ubuntu 24 VSCode Codex extension is infinite load

Eduardo7449 · 8 months ago

My VSCode Codex extension is infinite thinking and don't do nothing

etraut-openai contributor · 8 months ago

Thanks for reporting the problem. The service is down in some geographies. The team is working on it. Closing in favor of https://github.com/openai/codex/issues/7156.

lakibulParallax · 5 months ago

<img width="1154" height="643" alt="Image" src="https://github.com/user-attachments/assets/9331d219-75c9-4e0c-8ccc-2aae6d5563d7" />

Disable this (Run Codex In Windows Subsystem For Linux) option from Settings>Codex Settings fixed it for me

ankur237 · 5 months ago

Kindly go to your user name account and run the codex from command line and see what is the error. For my case it was VCC runtime error
Place of codex plugin installation:
C:\Users\Administrator\.vscode\extensions\openai.chatgpt-0.4.69-win32-x64\bin\windows-x86_64

Joserd1215 · 5 months ago

Tengo codex vscode extentions y no funciona, se queda cargando en cualquier version

stanevers · 5 months ago

I had the same issue after renaming the root project folder. After renaming it back to its original name Codex worked again.

asthanayak-netizen · 3 months ago

I am also facing the same issues . None of the above solutions worked for me. Please help

anhquan3302 · 2 months ago

<img width="985" height="722" alt="Image" src="https://github.com/user-attachments/assets/5826b111-d5e3-4be6-b805-4105a467d7dd" />

Could you help me? My Codex is unloading after the update. How can I repair it?

ndvbd · 10 days ago

Same issue here