Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix High CPU and disk usage on Windows immediately after Codex file edits when the changed-files result card appears [2 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#17159•Fetched 2026-04-09 08:01:45
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
swebdevelopersswebdevelopers
Participants
github-actions[bot]github-actions[bot]swebdevelopersswebdevelopers
Timeline (top)
labeled ×3commented ×2closed ×1

Error Message

I did not get a textual error message. The problem is performance degradation triggered by the Codex edit result UI after agent-applied file changes.

RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

openai.chatgpt-26.325.31654-win32-x64

What subscription do you have?

ChatGPT Business

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Using Codex in VS Code on Windows causes very high CPU and noticeable disk usage immediately after any agent-driven file edit is applied.

The issue does not depend on the project, language, or build system. I reproduced it with:

a .NET project a PHP project a nearly empty folder on Desktop even creating a brand new 1-line file The spike happens right when the Codex UI shows the changed-files result card after the edit, for example a card like:

"Changed 1 file" file path line delta such as "+1 -0" action buttons like "Undo" / "Review" Important details:

Manual edits in the editor do not cause this problem. Codex edits do cause it. It reproduces even without running build commands. It reproduces even in a new clean VS Code profile. Disabling Git in VS Code did not help. I also reproduced it in another folder outside the original workspace. Reloading the VS Code window temporarily clears the high CPU state. Minimal reproduction:

Open any folder in VS Code on Windows. Start a Codex session. Ask Codex to make a tiny file edit, for example add a single comment to a file, or create a new file containing only <?php. As soon as the changed-files result card appears in the Codex UI, CPU and disk usage spike. Expected result:

Codex applies the edit and VS Code remains responsive. Actual result:

One of the internal Code.exe processes starts using high CPU immediately after the edit result UI appears. VS Code becomes heavy/sluggish until I reload the window. I did not get a textual error message. The problem is performance degradation triggered by the Codex edit result UI after agent-applied file changes.

What steps can reproduce the bug?

Open VS Code on Windows. Open any folder. Start a Codex session. Ask Codex to make a very small file change. Wait for the changed-files result card to appear in the Codex UI. Observe CPU and disk usage in Task Manager. Result:

CPU usage increases immediately after the changed-files result card appears. VS Code becomes sluggish until I use Reload Window

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

Reloading the VS Code window may temporarily clear the high CPU state caused by Codex edits.

Guidance

  • Investigate the Codex UI's changed-files result card to determine if it's triggering an unnecessary process or resource-intensive operation.
  • Try disabling any unnecessary extensions or plugins in VS Code to see if they're contributing to the high CPU usage.
  • Monitor the internal Code.exe processes in Task Manager to identify which specific process is causing the high CPU usage.
  • Consider reporting this issue to the Codex or VS Code development teams for further investigation and potential fixes.

Example

No specific code snippet is applicable in this case, as the issue appears to be related to the interaction between Codex and VS Code.

Notes

The root cause of the issue is unclear, but it seems to be related to the way Codex interacts with VS Code after applying file edits. Further investigation is needed to determine the exact cause and develop a permanent fix.

Recommendation

Apply workaround: Reloading the VS Code window temporarily clears the high CPU state, and this can be used as a temporary workaround 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…
#runtime error#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING