Codex VS Code WSL app-server stuck at 70–90% CPU with outbound queue is full

Open 💬 3 comments Opened May 1, 2026 by mkikunda

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Hello,

I am using Codex VS Code extension with ChatGPT Pro on Windows + WSL Ubuntu.

Codex is installed only in WSL: Ubuntu, not locally anymore.

Extension version:
openai.chatgpt 26.422.71525

Problem:
As soon as I open the Codex panel, the local Codex app-server starts consuming 70–90% CPU and the panel becomes unusable.

Process shown in WSL:
~/.vscode-server/extensions/openai.chatgpt-26.422.71525-linux-x64/bin/linux-x86_64/codex app-server --analytics-default-enabled

Logs:
codex_app_server::transport: dropping overload response for connection ConnectionId(0):
outbound queue is full

Sometimes the process remains as:
[codex] <defunct>

I already tried:

uninstalling and reinstalling the extension
removing the local installation and keeping only WSL
killing codex app-server
wsl --shutdown
restarting VS Code
reconnecting/reloading the window

The issue persists after reinstall.

Please advise or provide a workaround/rollback version.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 3 months ago

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

#20029
#19608
#19434
#20212
#20295

Powered by Codex Action

mkikunda · 3 months ago

Additional confirmation:

This issue also happens after keeping Codex installed only under WSL: Ubuntu and removing the local Windows installation.

The process immediately restarts when the Codex panel is opened and consumes high CPU again.

Latest observed process:
~/.vscode-server/extensions/openai.chatgpt-26.422.71525-linux-x64/bin/linux-x86_64/codex app-server --analytics-default-enabled

Observed CPU:
70–90%

Observed log:
codex_app_server::transport: dropping overload response for connection ConnectionId(0):
outbound queue is full

After killing the process, it sometimes remains as:
[codex] <defunct>

This looks closely related to the duplicate issues detected by GitHub Actions, especially #20029 and #19608, but I am keeping this issue open because this is happening specifically with WSL Ubuntu on Windows and the latest extension version.

sabeti · 3 months ago

I'm having the exact same issue, however, my panel isn't locked out, though the CPU usage is high for the same process mentioned above.

Extension version: 26.429.30905