Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix [VS Code extension][Windows] High CPU regression after 26.325.31654 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19746•Fetched 2026-04-28 06:37:53
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
blueGLSblueGLS
Participants
blueGLSblueGLSgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.406.31014

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11

What issue are you seeing?

Opening the Codex VS Code extension panel causes one logical CPU to stay 60% - 80% (even though no session has been started). Closing the Codex panel immediately drops CPU usage.

What steps can reproduce the bug?

Steps to reproduce:

  1. Start VS Code with code --profile CodexTest
  2. Install only the Codex extension
  3. Open VS Code with no folder, only Untitled-1
  4. Open the Codex extension panel
  5. CPU usage rises and one logical CPU stays 60% - 80%.
  6. Close the Codex panel
  7. CPU usage immediately drops

What is the expected behavior?

Opening the Codex panel while idle should not continuously pin one logical CPU.

Additional information

Any suspicious applications, for example GoogleDrive etc. are closed beforehand.

extent analysis

TL;DR

The issue can likely be mitigated by disabling or uninstalling the Codex extension in VS Code to prevent excessive CPU usage.

Guidance

  • Verify that the issue is specific to the Codex extension by testing other extensions in VS Code to see if they cause similar CPU usage spikes.
  • Try updating the Codex extension to the latest version, if available, to see if the issue is resolved.
  • If the issue persists, consider filing a bug report with the Codex extension developers, providing the steps to reproduce the issue.
  • To work around the issue, consider keeping the Codex panel closed when not in use to prevent unnecessary CPU usage.

Example

No code snippet is provided as this issue appears to be related to the Codex extension's behavior rather than a code-specific problem.

Notes

The cause of the issue is likely related to the Codex extension's background processing or initialization when the panel is opened. Without more information about the extension's internal workings, it's difficult to provide a more specific fix.

Recommendation

Apply workaround: Closing the Codex panel when not in use can help mitigate the excessive CPU usage until a more permanent fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#authentication setup#request error#file not found#serialization error#model compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix [VS Code extension][Windows] High CPU regression after 26.325.31654 [1 comments, 2 participants]