Codex appears to leave orphaned git.exe processes on Windows.

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

26.527.7698.0

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

In one Codex App session on Windows, Codex opened many git.exe and Windows shell processes. After the task/session ended, several of these processes were still running.

This happened while I was asking Codex to make several changes and put each completed step/change into a PR. During that workflow, Codex repeatedly ran Git and shell commands.

At one point, I had around 30 git.exe processes open at the same time, plus multiple Windows shell processes. Today I manually closed around 20 git.exe processes and around 10 Windows command/shell processes.

Codex sometimes says that a process was closed, but Task Manager / PowerShell still shows the process running.

What steps can reproduce the bug?

I am using the Codex Desktop App from the Windows Store on Windows 10 Pro.

I do not have an exact minimal reproduction yet, but this happened during a normal Codex App workflow in my project:

1 I opened my project in the Codex Desktop App.
2 I gave Codex multiple tasks and asked it to put each completed step/change into a PR.
3 Codex ran Git commands and Windows shell commands during the session.
4 After a while, I noticed that many processes were still open.
5 Task Manager / PowerShell showed around 30 git.exe processes and multiple Windows command/shell processes still running.
6 Today I manually closed around 20 git.exe processes and around 10 Windows processes.
7 In some cases Codex said that a process was closed, but the process was still visible and running in Windows.

Example from PowerShell:

Remaining process: git.exe
PID: 24612
Started: 2026-06-02 18:21:10
Path: C:\Program Files\Git\mingw64\libexec\git-core\git.exe

I am not sure if the PR workflow specifically triggers the issue, but it happened while Codex was repeatedly creating/working with PRs and running Git commands.

What is the expected behavior?

Codex should clean up all Git, shell, and child processes that it starts during a session.

If Codex starts git.exe, cmd.exe, powershell.exe, node.exe, or other child processes, it should track their PIDs and terminate them when they are no longer needed.

If Codex says that a process was closed, the process should actually be terminated and no longer appear in Task Manager or PowerShell.

Additional information

_No response_