High CPU and disk usage on Windows immediately after Codex file edits when the changed-files result card appears

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_