What happened?
After updating Codex to the latest Windows version, my development machine becomes very slow. In Windows Task Manager, CPU is continuously consumed by multiple Git for Windows processes while Codex is open during development.
I manage version control manually and did not explicitly ask Codex to run any Git operation. The Git processes appear to be spawned repeatedly by Codex or by its integration while working in a local project.
Impact
- Windows 11 becomes noticeably laggy during development.
- CPU remains high for a long time.
- Multiple
Git for Windows / git.exe processes are visible in Task Manager.
- This makes the current Windows Codex workflow difficult to use.
Environment
- OS: Windows 11
- Git: Git for Windows
- Codex: latest Windows version available at the time of reporting
- Shell/IDE: Windows development environment; also considering PowerShell CLI because WSL is not available on this machine
Screenshot / observation
Task Manager shows multiple Git for Windows processes, each consuming CPU, while Codex is running.
Expected behavior
Codex should not continuously spawn Git processes or keep Git CPU usage high when idle or during normal development. Ideally there should also be a setting to disable Codex Git integration, since some users manage Git manually.
Actual behavior
After the recent update, Codex appears to repeatedly invoke Git, causing sustained CPU usage and system lag.
Request
Could you please check whether the recent Windows build introduced a Git polling / metadata loop? Also, is there any supported configuration to disable Git integration or reduce Git polling frequency in Codex on Windows?
Potentially related reports:
- Windows desktop app repeatedly spawning
git.exe / git add -A / git rev-parse
- Windows app repeatedly running Git commands at high frequency
- Git metadata retry loop in non-standard or non-Git workspaces
I can provide more details if needed, such as process tree, exact Codex version, workspace layout, or logs.
What happened?
After updating Codex to the latest Windows version, my development machine becomes very slow. In Windows Task Manager, CPU is continuously consumed by multiple Git for Windows processes while Codex is open during development.
I manage version control manually and did not explicitly ask Codex to run any Git operation. The Git processes appear to be spawned repeatedly by Codex or by its integration while working in a local project.
Impact
Git for Windows/git.exeprocesses are visible in Task Manager.Environment
Screenshot / observation
Task Manager shows multiple
Git for Windowsprocesses, each consuming CPU, while Codex is running.Expected behavior
Codex should not continuously spawn Git processes or keep Git CPU usage high when idle or during normal development. Ideally there should also be a setting to disable Codex Git integration, since some users manage Git manually.
Actual behavior
After the recent update, Codex appears to repeatedly invoke Git, causing sustained CPU usage and system lag.
Request
Could you please check whether the recent Windows build introduced a Git polling / metadata loop? Also, is there any supported configuration to disable Git integration or reduce Git polling frequency in Codex on Windows?
Potentially related reports:
git.exe/git add -A/git rev-parseI can provide more details if needed, such as process tree, exact Codex version, workspace layout, or logs.