What issue are you seeing?
Codex.exe appeared to continue running in the background even though I did not have the Codex app window open. It repeatedly launched many git.exe add -A processes against my repository. Each git add -A spawned git-lfs.exe filter-process --skip, eventually creating a large number of Git/Git-LFS processes.
This appears to be a Codex Git/background task handling bug. Git LFS itself was not the initiating process; it was a child of the repeated git add -A commands.
Observed process chain:
Codex.exe PID 8516
-> git.exe add -A
-> git-lfs.exe filter-process --skip
Example process list excerpt:
42640 61660 git.exe git.exe add -A
48180 80692 git.exe git.exe add -A
86296 66500 git.exe git.exe add -A
33640 96260 git-lfs.exe "C:\Program Files\Git\mingw64\bin\git-lfs.exe" filter-process --skip
4052 50740 git-lfs.exe "C:\Program Files\Git\mingw64\bin\git-lfs.exe" filter-process --skip
...
45208 29912 git.exe "C:\Program Files\Git\cmd\git.exe" add -A
Parent process identification:
ProcessId : 29912
ParentProcessId : 8516
Name : Codex.exe
CommandLine : "C:\Program Files\WindowsApps\OpenAI.Codex_26.506.3741.0_x64__2p2nqsd0c76g0\app\Codex.exe"
What steps can reproduce the bug?
Environment:
- OS: Windows
- App: Codex Windows app
- Package path observed:
C:\Program Files\WindowsApps\OpenAI.Codex_26.506.3741.0_x64__2p2nqsd0c76g0\app\Codex.exe
- Repo uses Git LFS for large
.stl / .jpg assets
- Git LFS config included:
[filter "lfs"]
clean = git-lfs clean -- %f
smudge = git-lfs smudge --skip -- %f
process = git-lfs filter-process --skip
required = true
Trigger/context:
I had unzipped a large archive into the repository. The repository contains many Git LFS-tracked assets. I did not intentionally run git add -A, and I did not have the Codex app visibly open at the time.
What is the expected behavior?
Expected behavior:
Codex should not repeatedly run git add -A in the background without explicit user action, especially in a repository with many large Git LFS-tracked assets. If Codex needs to inspect Git state, it should avoid staging files, or should do so only with explicit approval and concurrency limits.
Additional information
Actual behavior:
Codex repeatedly spawned git.exe add -A processes. This caused many git-lfs.exe filter-process --skip processes to run concurrently and made the machine/repo unstable until the Codex parent process was killed.
Resolution/workaround:
Killing the Codex parent process stopped the spawning
What issue are you seeing?
Codex.exe appeared to continue running in the background even though I did not have the Codex app window open. It repeatedly launched many git.exe add -A processes against my repository. Each git add -A spawned git-lfs.exe filter-process --skip, eventually creating a large number of Git/Git-LFS processes.
This appears to be a Codex Git/background task handling bug. Git LFS itself was not the initiating process; it was a child of the repeated git add -A commands.
Observed process chain:
Codex.exe PID 8516
-> git.exe add -A
-> git-lfs.exe filter-process --skip
Example process list excerpt:
42640 61660 git.exe git.exe add -A
48180 80692 git.exe git.exe add -A
86296 66500 git.exe git.exe add -A
33640 96260 git-lfs.exe "C:\Program Files\Git\mingw64\bin\git-lfs.exe" filter-process --skip
4052 50740 git-lfs.exe "C:\Program Files\Git\mingw64\bin\git-lfs.exe" filter-process --skip
...
45208 29912 git.exe "C:\Program Files\Git\cmd\git.exe" add -A
Parent process identification:
ProcessId : 29912
ParentProcessId : 8516
Name : Codex.exe
CommandLine : "C:\Program Files\WindowsApps\OpenAI.Codex_26.506.3741.0_x64__2p2nqsd0c76g0\app\Codex.exe"
What steps can reproduce the bug?
Environment:
C:\Program Files\WindowsApps\OpenAI.Codex_26.506.3741.0_x64__2p2nqsd0c76g0\app\Codex.exe.stl/.jpgassetsTrigger/context:
I had unzipped a large archive into the repository. The repository contains many Git LFS-tracked assets. I did not intentionally run git add -A, and I did not have the Codex app visibly open at the time.
What is the expected behavior?
Expected behavior:
Codex should not repeatedly run git add -A in the background without explicit user action, especially in a repository with many large Git LFS-tracked assets. If Codex needs to inspect Git state, it should avoid staging files, or should do so only with explicit approval and concurrency limits.
Additional information
Actual behavior:
Codex repeatedly spawned git.exe add -A processes. This caused many git-lfs.exe filter-process --skip processes to run concurrently and made the machine/repo unstable until the Codex parent process was killed.
Resolution/workaround:
Killing the Codex parent process stopped the spawning