›_ Codex Issues
Codex Issues / #24910

Windows Codex App 26.519.11010.0 flashes git.exe console windows during tasks

Open 💬 5 comments Opened May 28, 2026 by rwang23

What version of the Codex App are you using?

OpenAI.Codex_26.519.11010.0_x64__2p2nqsd0c76g0

The app package reported locally:

Name: OpenAI.Codex
Version: 26.519.11010.0
PackageFullName: OpenAI.Codex_26.519.11010.0_x64__2p2nqsd0c76g0

What subscription do you have?

ChatGPT / Codex desktop app user. Please let me know if you need a more specific subscription value.

What operating system are you using?

Windows 11 x64.

What Git version are you using?

git version 2.54.0.windows.1

git resolves to:

D:\Software\Git\cmd\git.exe
D:\Software\Git\bin\git.exe

What issue are you seeing?

During normal Codex App task execution on Windows, a git.exe command-line window repeatedly flashes/pops up. The window appears almost instantly and disappears too quickly to read the full command; only git.exe is visible.

This started recently. Rebooting Windows multiple times and restarting Codex does not resolve it.

Based on local inspection, git.exe is the normal Git for Windows console executable. The visible popup looks consistent with Codex launching Git from the desktop GUI context without hiding the console window.

Why this seems app-side

  • The behavior happens while using Codex App tasks, not from a user-initiated terminal command.
  • Restarting Windows and reopening Codex does not fix it.
  • Git itself works normally from PowerShell.
  • The symptoms resemble earlier Windows app reports where Codex repeatedly spawned Git and conhost processes.

Related prior issues that look similar:

  • #17229: Codex Windows App repeatedly spawning git.exe status --porcelain=v1 -z and conhost.exe
  • #20933: Windows desktop app triggering multiple git.exe add -A / rev-parse processes when opening a project/chat
  • #20867: Windows desktop app update causing unresponsiveness and repeated Git metadata work

Expected behavior

Codex should be able to run Git status/snapshot commands on Windows without showing transient git.exe / console windows to the user. If Git is launched from the desktop app, it should use a hidden/no-window process creation mode.

Actual behavior

A git.exe console window repeatedly flashes during Codex task execution.

Additional notes

I considered a local workaround using a Git wrapper, but this should ideally be fixed in the app by launching Git with the appropriate Windows no-console/no-window flags rather than requiring users to replace or wrap Git.

View original on GitHub ↗

5 Comments

Happy-DJ · 2 months ago

May I ask if you have solved it?

rwang23 · 2 months ago

Not fully solved upstream yet. I think the real fix needs to come from the Codex Windows app itself: when it launches Git from the desktop/GUI process, it should start git.exe with the appropriate no-console/no-window flags.

For now I made a local temporary workaround here:

https://github.com/rwang23/codex-windows-console-guard

What it does:

  • does not replace or rename your real Git executable
  • does not modify system/user PATH
  • installs a small local git.exe wrapper under the user profile
  • starts Codex through a launcher that prepends the wrapper path only to that Codex process environment
  • the wrapper then starts the real Git executable with CREATE_NO_WINDOW

Basic usage:

git clone https://github.com/rwang23/codex-windows-console-guard.git
cd codex-windows-console-guard
powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1
powershell -ExecutionPolicy Bypass -File .\scripts\status.ps1
powershell -ExecutionPolicy Bypass -File .\scripts\start-codex-with-git-wrapper.ps1

If Git is installed in a custom location, use -RealGit, for example:

powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1 -RealGit "C:\Program Files\Git\cmd\git.exe"

Rollback:

powershell -ExecutionPolicy Bypass -File .\scripts\remove.ps1

This is only a workaround until Codex fixes the Windows Git process launch behavior officially.

rwang23 · 2 months ago

Update: I refreshed the workaround repo after seeing another Windows-specific edge case.

Repo: https://github.com/rwang23/codex-windows-console-guard

Changes:

  • The installer now prefers a native C++ GUI wrapper when a native compiler is available.
  • If no native compiler is available, it falls back to the managed C# wrapper.
  • The managed fallback no longer reads Environment.CurrentDirectory before launching Git. This avoids one .NET Runtime / fondue.exe failure mode I hit locally when Codex inherited a broken/unavailable working directory.
  • README now includes a fondue.exe / Windows Features troubleshooting section.

This is still only a local workaround for visible git.exe console windows. It does not reduce Codex's Git polling frequency; the upstream fix still needs Codex Desktop on Windows to launch internal Git subprocesses with hidden/no-window process flags.

suiyuebaobao · 1 month ago

The visible git.exe console-process churn reported here is part of the same Git-backed desktop integration surface that this workaround disables.

I published a single-file Windows launcher for the original Microsoft Store/MSIX Codex app:

It starts Codex with a process-scoped GIT_DIR=NUL. On my machine, the stable trace changed from 247 new git.exe and 137 new taskkill.exe processes per 10 seconds to 0 and 0 over 15 seconds; WMI Provider Host fell from about 6.6% to 0.9%.

Usage: fully exit Codex from the Windows system tray, then run the script.

This is an unofficial workaround, not an upstream fix. It deliberately disables or limits Review, Changes, branch detection, commit, and other Git-backed Codex features. It does not patch Codex, modify repositories or Git configuration, write system environment variables, require elevation, terminate processes, or remove chat history. Launching Codex normally restores Git integration.

shimtimultimedia · 1 month ago

Still present in 26.721.4979.0 — spawns visible powershell/conhost windows during tasks and up to one per second during connection retries, stealing keyboard focus.