# Codex Fails on Windows/Linux **URL:** \ **Category:** Codex CLI\ **Tags:** chatgpt\ **Created:** [July 22, 2026, 4:04am UTC](https://community.openai.com/t/codex-fails-on-windows-linux/1387777 "2026-07-22T04:04:24Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![seroncheng](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/seroncheng/32/747277_2.png) [@seroncheng](https://community.openai.com/u/seroncheng)\ **Post date:** [July 22, 2026, 4:04am UTC](https://community.openai.com/t/codex-fails-on-windows-linux/1387777/1 "2026-07-22T04:04:24Z")
Dear OpenAI Developers, I need to raise a serious issue today. I have always used Codex on my Mac, but today I decided to try it on my Windows PC through the official VS Code extension. It worked for a while, but after I closed VS Code and opened it again, the extension became completely stuck on the logo screen. There was no error message, no warning, and no explanation. I waited for more than half an hour, but nothing happened. I then downloaded the Windows desktop client. As soon as I opened it, it used more than 70% of my system memory. Even after I finally managed to get into the app, it was so laggy that typing a single sentence felt difficult. My Windows PC has an Intel i7-14900 processor and an RTX 4060 GPU. I do not consider this outdated hardware, so the performance was honestly unacceptable. At first, I thought the problem might be related to my Windows setup rather than the extension itself. To test this, I installed VS Code and the official Codex extension on my public Linux server. Unfortunately, I experienced exactly the same problem. After another half hour of waiting, it was still stuck on the logo screen. I am genuinely looking forward to future updates and improvements because I am a loyal user and a big supporter of OpenAI. On macOS, it feels like you release updates almost every day and continue making the experience better and better. However, after leaving the Mac environment, I realized that the Windows client and VS Code extension seem to receive nowhere near the same level of optimization. The difference is honestly unbelievable. I sincerely hope you can give a proper response to a loyal paying customer and explain whether these issues are being addressed. ---
**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\ **Post date:** [July 22, 2026, 10:51am UTC](https://community.openai.com/t/codex-fails-on-windows-linux/1387777/2 "2026-07-22T10:51:19Z")
You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for [OpenAI Codex](https://github.com/openai/codex/issues). I had ChatGPT look for the closest related issue and it identified: > > > \## Summary > > \*\*This is a VS Code platform bug, but Codex can and should defend ag…ainst it — and\*\*\*\*\\*\*\*\*right now it is silently eating a whole cluster of your "blank panel / stuck on\*\*\*\*\\*\*\*\*logo" reports.\*\* > > I was able to nail down the root cause on the Codex extension, so I am reporting it\here as well as upstream: > > \> After \`openai.chatgpt\` updates \*\*in place\*\*, VS Code's on-disk webview\service-worker cache keeps resolving \`webview/assets/\*.js\` against the \*\*previous\*\*\extension directory — which VS Code itself deletes on the next start. Every chunk\fails with \`net::ERR\_FAILED\`, the React app never mounts, and the panel shows\nothing but the OpenAI logo. Because the cache lives on disk, this survives a panel\reload, a window reload, a VS Code restart \*\*and a full machine reboot\*\*. > > Upstream report (root cause, full evidence): \[\*\*https://github.com/microsoft/vscode/issues/325767\*\*\](\) > > I only have a \*\*workaround\*\*, not a fix — see below. But the mitigation I am asking\for here is cheap and lives entirely on your side. > > \## Why this is your problem too > > The fix belongs to VS Code, but the last time this exact mechanism was reported\against an extension (\`anthropics/claude-code#13130\` — same bug, different vendor) it\was closed as \*not planned\* and nothing happened. Meanwhile these are all still open\in \*\*this\*\* tracker, all with the same symptom and no root cause found: > > \* openai/codex#32388 — Linux, VS Code \*\*1.128.0\*\*, extension \*\*26.707.41301\*\*: that is the\\*exact\* VS Code + extension version pair I reproduced this on. The reporter's\accidental workaround (\`code --disable-extension \\`) is consistent with a\cache/startup-state artifact rather than an extension conflict. > \* openai/codex#15975 — "stuck on loading/logo screen after VS Code update", no maintainer response. > \* openai/codex#28280 — "Codex panel empty in VS Code". > > I would bet a good share of these are one bug. > > \## What I ask for > > 1. \*\*Force a window reload after an in-place update.\*\* The extension knows its own\version. If the running version differs from the version the webview was built\against, prompt for (or force) \*Reload Window\* rather than rendering into a resource\map that can no longer resolve. This alone would make the panel immune, regardless of\what VS Code does. > 2. \*\*Version-stamp the webview asset URLs.\*\* If the asset URLs carried the extension\version, a stale service-worker entry could not silently shadow the new build. > 3. \*\*Detect and surface it.\*\* If the webview's asset fetches fail, say so in the panel\("the extension was updated — reload the window") instead of showing a logo forever.\The current failure mode is undiagnosable for a normal user: \*every\* log is green. > > \## Evidence > > Environment: Debian 12 (bookworm), kernel 6.1.0-50, x64 · VS Code 1.128.0\(\`fc3def6774c76082adf699d366f31a557ce5573f\`) · \`openai.chatgpt\` 26.707.71524\(previously 26.707.41301, before that 26.707.31428) · ChatGPT sign-in,\\`codex login status\` green throughout. > > \*\*1. VS Code deletes the old extension dir the cache still points at\*\* —\\`~/.config/Code/logs/20260714T120150/sharedprocess.log\`: > > \`\`\` > 2026-07-14 12:01:55.024 \[info\] Marked extension as removed openai.chatgpt-26.707.41301-linux-x64 > 2026-07-14 12:01:56.557 \[info\] Deleted marked for removal extension from disk openai.chatgpt /home/tg/.vscode/extensions/openai.chatgpt-26.707.41301-linux-x64 > \`\`\` > > Only the new directory remains, and there is no stale \`openai.chatgpt\` entry in\\`.obsolete\` — so this is \*\*not\*\* the "old folders left behind" theory from\\`anthropics/claude-code#13130\`. Cleanup is clean; the cache is simply never told. > > \*\*2. The cache predates the new extension.\*\* mtimes in the broken state: > > \`\`\` > 2026-07-14 09:45:41 ~/.vscode/extensions/openai.chatgpt-26.707.71524-linux-x64 \<- new extension > 2026-07-12 16:17:52 ~/.config/Code/Service Worker \<- built while 41301 was live > 2026-07-12 16:17:49 ~/.config/Code/{Cache,Code Cache,CachedData,GPUCache} > \`\`\` > > \*\*3. The Codex backend is completely healthy — it is purely the webview.\*\*\\`window1/exthost/openai.chatgpt/Codex.log\` from the broken session: > > \`\`\` > 2026-07-14 12:01:54.428 \[info\] Activating Codex extension > 2026-07-14 12:01:54.428 \[info\] \[CodexMcpConnection\] Spawning codex app-server > 2026-07-14 12:01:56.106 \[info\] \[CodexMcpConnection\] Initialize received id=1 > \`\`\` > > \`renderer.log\` and \`exthost.log\`: no errors at all. \*\*This is the trap.\*\* Everyone\debugging this — including me, the first time — goes after the \`app-server\` or the\auth, because that is where you would look. Both are fine. My \`id\_token\` had been\expired for days and it was \*still\* irrelevant. > > \*\*4. The only place the error appears — \*Developer: Open Webview Developer Tools\* → Console:\*\* > > \`\`\` > Failed to load resource: net::ERR\_FAILED .../webview/assets/\.js > \`\`\` > > …for chunks that \*\*exist on disk\*\* under the new extension path. > > \*Full disclosure:\* that console capture is from the first occurrence (2026-07-12). On\the second (2026-07-14) I went straight to the fix and did not re-open DevTools; all\other evidence above is from 2026-07-14. > > \## Workaround for anyone landing here > > Delete VS Code's caches \*\*with VS Code shut down\*\* (pure caches — settings and\extensions are untouched, VS Code rebuilds them): > > \`\`\`bash > pkill -TERM -f '/usr/share/code/code' # and wait for it to actually exit > rm -rf ~/.config/Code/{"Service Worker",Cache,"Code Cache",GPUCache,CachedData} > rm -rf /tmp/codex-ipc > code > \`\`\` > > 2 / 2 successful. What does \*\*not\*\* work: reloading the panel, \*Reload Window\*,\restarting VS Code, rebooting, killing the app-server, re-authenticating. > > Diagnosis shortcut, faster than opening DevTools: if\\`~/.vscode/extensions/openai.chatgpt-\*\` is \*\*newer\*\* than\\`~/.config/Code/Service Worker\`, you have this bug. If that issue matches your problem, consider adding a 👍 reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work. If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible. ---
**Author:** ![sps](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sps/32/7736_2.png) [@sps](https://community.openai.com/u/sps)\ **Post date:** [July 22, 2026, 6:39pm UTC](https://community.openai.com/t/codex-fails-on-windows-linux/1387777/3 "2026-07-22T18:39:23Z")
Thank you for the detailed report and for your patience. A fix was rolled out today that should address these issues. Please download and install the latest ChatGPT unified app build: - Windows: 26.715.10079.0 - macOS: 26.715.72359 After updating, please let us know if you continue to experience loading or performance issues. Your feedback will help us investigate further if needed. ---
**Author:** ![system](https://us1.discourse-cdn.com/openai1/original/4X/8/7/c/87c2e81543bbb01aa9641aeef8fe14cab5e9590a.png) [@system](https://community.openai.com/u/system)\ **Post date:** [July 25, 2026, 6:40pm UTC](https://community.openai.com/t/codex-fails-on-windows-linux/1387777/4 "2026-07-25T18:40:22Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.