VS Code extension host Code Helper (Plugin) high CPU with repeated thread-stream-state-changed warnings on macOS
Summary
When I open the Codex VS Code extension and start using it in a single VS Code window, CPU usage rises significantly and the machine heats up.
The dominant process is the VS Code extension host (Code Helper (Plugin)), not the Codex backend itself. This looks related to #3022 and possibly adjacent to #7456 / #7473, but my main symptom is extension-host CPU plus repeated warning spam in the Codex logs.
Environment
- macOS 26.4 (25E246)
- Apple Silicon
- OpenAI VS Code extension
openai.chatgpt26.325.31654 - Single VS Code window
Observed behavior
At the time of capture:
Code Helper (Plugin): about 36.4% CPUcodex app-server: about 2.1% CPU
The issue appears specifically when the Codex extension is active.
Reproduction
- Open VS Code.
- Open the OpenAI / Codex extension.
- Start or resume a chat session.
- CPU usage rises and the machine heats up.
Logs
The logs repeatedly contain:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
Examples from one affected session:
Codex.log:12Codex.1.log:1461Codex.3.log:255Codex.3.log:256Codex.3.log:265
The session log directory also rotated quickly and produced multiple large files:
Codex.1.logthroughCodex.6.log: 5.0 MB eachCodex.log: 2.5 MB
Local log path:
~/Library/Application Support/Code/logs/20260402T162242/window3/exthost/openai.chatgpt/
Expected behavior
The extension should not drive sustained high CPU usage in the VS Code extension host during normal chat usage.
Related issues
- #3022
- #7456
- #7473
I can provide full logs if needed.
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Closing as a duplicate of #16231. The exact warning loop also closely matches #15397 (). I moved my concrete CPU snapshot and log details into #16231 so the data stays attached to the more established thread.
Closing note: this is best tracked under #16231 for the
26.325.31654regression on macOS. The exact warning loop also closely matches #15397 (thread-stream-state-changed).I moved my concrete CPU snapshot and log details into #16231 so the evidence stays attached to the more established thread.