VS Code Codex extension hangs after completing edits and keeps CMD running with high CPU

What version of the IDE extension are you using?

Codex extension 0.4.74

What subscription do you have?

PLUS

Which IDE are you using?

VS Code 1.109.3

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

After Codex finishes the requested code edits, it starts a CMD process in the background and appears to hang for a very long time.
The edits are already applied correctly, but the terminal process keeps running with high CPU usage and no new output.
I have to manually end the task from Task Manager.

Expected behavior:
Once edits are completed, the extension should stop background commands (or timeout safely) and return control immediately.

Actual behavior:
Background CMD process continues indefinitely (or for a very long time), high CPU usage, no progress output.

Environment:

• OS: Windows 11
• Editor: Visual Studio Code
• Extension: Codex VS Code extension
• Shell: CMD
• Project type: [your project type here]
• Reproducibility: [Always / Often / Sometimes]

Steps to reproduce:

1. Open project in VS Code.
2. Ask Codex extension to apply code changes.
3. Wait until edits are done.
4. Observe CMD process starts/continues in background with high CPU and no output.
5. Need to kill process manually via Task Manager.

What I already tried:

• Restarted VS Code
• Restarted Windows
• Disabled other extensions temporarily
• Reproduced in another workspace

Attachments:

• Screenshot of terminal/CMD stuck state
• Task Manager screenshot showing CPU usage
• Relevant extension logs/output

What steps can reproduce the bug?

1. Open Visual Studio Code on Windows 11.
2. Open any project folder (I reproduced this in more than one workspace).
3. Start the Codex extension and ask it to apply code changes.
4. Wait until Codex finishes editing files.
5. After edits are done, the extension starts/keeps a CMD process running in the background.
6. Observe that CPU usage stays high and there is no new terminal output/progress.
7. Wait several minutes (e.g., 10+), the process still does not exit.
8. Manually end the process from Task Manager to recover.

What is the expected behavior?

_No response_

Additional information

_No response_