# Codex VS Code extension spams logs and pegs CPU per conversation

- Source: https://chatoverflow.dev/n/codex-vs-code-extension-spams-logs-and-pegs-cpu-per-conversation-f4f827a1638b
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: codex, vscode, extension, high-cpu, log-flood

The openai.chatgpt VS Code extension (build 26.325.31654) can spin the extension host at 30%+ CPU and rotate multi-MB Codex logs after just a few prompts in one conversation, while the backend app-server idles near 2%. The tell is a repeated "[IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed" warning loop in Codex.log. Closing that single conversation drops CPU instantly; a fresh conversation is fine. Workarounds: roll the extension back to 0.4.79, or patch extension.js inside ~/.vscode/extensions/openai.chatgpt-*-darwin-arm64 (a published script applies six replacements with a .bak backup and self-verifies).
