Description
The Codex Windows desktop app opens successfully but remains permanently stuck on the loading spinner.
The browser version of ChatGPT works normally.
Environment
- Windows 11 25H2
- Build: 26200.9457
- OpenAI Codex package: OpenAI.Codex
- Desktop version: 26.924.2738.0
- Package family: OpenAI.Codex_2p2nqsd0c76g0
Expected behavior
The Codex desktop UI should finish loading and show the normal application interface / composer.
Actual behavior
The window opens, but remains indefinitely on the loading spinner.
The app does not crash and the backend continues running.
Diagnostics
The following components start successfully:
- ChatGPT.exe main process
- Chromium renderer processes
- GPU process
- Network service
- Storage service
- codex.exe app-server
Authentication works and backend communication is active.
The Codex models endpoint returns HTTP 200.
The MSIX/AppX application activation succeeds.
Chromium / Electron debugging
I launched the application with:
--enable-logging --v=1 --remote-debugging-port=9222
The DevTools endpoint works on:
127.0.0.1:9222
The main renderer target is:
app://-/index.html
A direct WebSocket connection to the Chrome DevTools Protocol for this renderer succeeds (STATE: Open).
The renderer repeatedly reports:
Matched leaf route at location "/" does not have an element or Component.
This means it will render an with a null value by default resulting in an "empty" page.
Source:
app://-/assets/app-initial-ff48311587c5.js
The renderer continues making backend requests after this warning, including requests for:
- account information
- user settings
- sites/access
- task list
- usage
- onboarding context
- automations
No fatal JavaScript exception has been found in the Electron renderer log so far.
Troubleshooting already performed
- Reinstalled the desktop application
- Windows Repair / Reset
- Tested another network / mobile hotspot
- Checked WebView2
- Tested GPU-disabled launch
- Tested with a clean Chromium/Electron profile
- Isolated Codex thread history
- Isolated session data
- Isolated state_5.sqlite
- Isolated .codex-global-state.json
- Verified SQLite integrity
- Tested without plugin/temp state
- Checked AppModel Runtime / TWinUI activation
- Checked Windows Defender Controlled Folder Access
Controlled Folder Access had previously blocked some Codex helper/sandbox processes. Those permissions were corrected and Codex CLI sandbox/write tests now succeed. The desktop spinner issue remains unchanged.
Logs available
I can provide, after redacting sensitive information:
- Electron debug log
- Codex app-server logs
- Windows Event Viewer logs
- process trees / command lines
- AppModel / TWinUI activation logs
- Codex session transcripts
- screenshots
I cannot generate an in-app feedback Session ID because the desktop app never reaches the composer.
Please let me know which additional diagnostic information would be useful.
Description
The Codex Windows desktop app opens successfully but remains permanently stuck on the loading spinner.
The browser version of ChatGPT works normally.
Environment
Expected behavior
The Codex desktop UI should finish loading and show the normal application interface / composer.
Actual behavior
The window opens, but remains indefinitely on the loading spinner.
The app does not crash and the backend continues running.
Diagnostics
The following components start successfully:
Authentication works and backend communication is active.
The Codex models endpoint returns HTTP 200.
The MSIX/AppX application activation succeeds.
Chromium / Electron debugging
I launched the application with:
--enable-logging --v=1 --remote-debugging-port=9222
The DevTools endpoint works on:
127.0.0.1:9222
The main renderer target is:
app://-/index.html
A direct WebSocket connection to the Chrome DevTools Protocol for this renderer succeeds (
STATE: Open).The renderer repeatedly reports:
Matched leaf route at location "/" does not have an element or Component.
This means it will render an with a null value by default resulting in an "empty" page.
Source:
app://-/assets/app-initial-ff48311587c5.js
The renderer continues making backend requests after this warning, including requests for:
No fatal JavaScript exception has been found in the Electron renderer log so far.
Troubleshooting already performed
Controlled Folder Access had previously blocked some Codex helper/sandbox processes. Those permissions were corrected and Codex CLI sandbox/write tests now succeed. The desktop spinner issue remains unchanged.
Logs available
I can provide, after redacting sensitive information:
I cannot generate an in-app feedback Session ID because the desktop app never reaches the composer.
Please let me know which additional diagnostic information would be useful.