codex - 💡(How to fix) Fix Codex Windows App keeps spawning `git.exe status --porcelain=v1 -z` and leaves orphan `git.exe` / `conhost.exe` processes [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#17229Fetched 2026-04-10 03:43:41
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

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

26.325.3894.0

What subscription do you have?

On Windows, the Codex Windows App repeatedly spawns Git processes such as: - git.exe status --porcelain=v1 -z and also creates matching console host processes such as: - \??\C:\WINDOWS\system32\conhost.exe 0x4 After closing the Codex window, new processes stop appearing, but many existing git.exe / conhost.exe processes remain alive. Even after ending Codex.exe from Task Manager, the leftover Git-related processes are still present. This looks like the app is polling Git state very aggressively and not cleaning up child processes correctly on exit.

What platform is your computer?

No response

What issue are you seeing?

<img width="2240" height="1239" alt="Image" src="https://github.com/user-attachments/assets/1638cc0a-dd13-461a-b128-7614c7bb6674" /> <img width="1161" height="789" alt="Image" src="https://github.com/user-attachments/assets/baabcb72-da01-4fc6-ae1c-b899d018b3a0" /> <img width="1161" height="790" alt="Image" src="https://github.com/user-attachments/assets/d55da594-4891-4a19-9aa3-b41c6d8b786a" />

C:\Users\root\Documents\New project\ is the default project directory used by Codex.

What steps can reproduce the bug?

  1. Open Codex Windows App.
  2. Open a Git repository.
  3. Observe Task Manager / Process Explorer.
  4. Notice repeated creation of:
    • git.exe status --porcelain=v1 -z
    • conhost.exe 0x4
  5. Close the Codex app window.
  6. New Git processes stop appearing, but many previously created git.exe / conhost.exe processes remain.
  7. End Codex.exe manually in Task Manager.
  8. Leftover git.exe / conhost.exe processes are still not cleaned up.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue can be mitigated by manually terminating the leftover Git-related processes after closing the Codex app.

Guidance

  • Verify that the issue is indeed caused by the Codex app's aggressive polling of Git state by monitoring the process creation and termination in Task Manager or Process Explorer.
  • Attempt to reproduce the issue with a minimal Git repository to see if the problem persists.
  • Consider using a task automation tool or script to automatically terminate the leftover Git-related processes after the Codex app is closed.
  • Investigate if there are any Codex app settings or configuration options that can be adjusted to reduce the frequency of Git state polling.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The provided information does not mention the expected behavior, which might be useful in understanding the root cause of the issue. Additionally, the platform of the computer is not specified, which could be relevant in troubleshooting the issue.

Recommendation

Apply workaround: Manually terminate the leftover Git-related processes after closing the Codex app, as this is a straightforward and effective way to mitigate the issue, although it may not address the underlying cause.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING