What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.417.41555 (1858)
What subscription do you have?
Pro 5x
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Codex Desktop on macOS launches 3 Codex Helper (Renderer) processes for a single visible window, and 2 of those renderers stay pinned around 118% to 131% CPU even when the app is idle or lightly used. At the same time, the renderer logs repeatedly emit worker_rpc_response_error errorMessage="Not a git repository" method=stable-metadata workerId=git. This continues after restarting the app and after resetting Codex app state.
bug-report-artifacts.tar.gz
What steps can reproduce the bug?
Uploaded thread: 019dac38-5275-7540-a26e-26250e368f5a
Open Codex Desktop on macOS.
Open or restore a normal Codex window/thread.
Let the app sit idle or use it lightly.
Open Activity Monitor.
Observe that there are 3 Codex Helper (Renderer) processes and that 2 of them stay above 100% CPU.
Check the Codex logs under ~/Library/Logs/com.openai.codex/ and observe repeated stable-metadata / Not a git repository errors.
What is the expected behavior?
Codex Desktop should not keep multiple renderer processes pinned above 100% CPU when only one window is open and the app is idle or lightly used. Git metadata checks should fail gracefully without creating a high-volume renderer error loop or sustained CPU usage.
Additional information
I already tried multiple local fixes and the issue still reproduces:
- quit and relaunch Codex
- reset
~/Library/Application Support/Codex
- reset broader OpenAI desktop state under
~/Library/Application Support/com.openai.chat
- recreate missing workspace paths
- initialize Codex scratch folders as git repositories
- add initial commits, local
origin config, and local origin/main / origin/HEAD refs to those scratch repos
None of those steps fixed the problem.
Environment:
- Codex Desktop
26.417.41555
- Build
1858
- Electron
41.2.0
- macOS
26.5 (25F5058e)
- Apple Silicon /
arm64
Most recent observed process state:
- 1 visible Codex window
- 3 renderer processes
- 2 renderers around
118% to 131% CPU
Relevant log pattern:
worker_rpc_response_error errorMessage="Not a git repository" method=stable-metadata workerId=git
In one fresh restart log, I counted 22,894 occurrences of that error.
Related issues that may be relevant:
#18545 (macOS renderer / WindowServer CPU)
#18515 (stable-metadata git log loop, VS Code extension)
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.417.41555 (1858)
What subscription do you have?
Pro 5x
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Codex Desktop on macOS launches 3 Codex Helper (Renderer) processes for a single visible window, and 2 of those renderers stay pinned around 118% to 131% CPU even when the app is idle or lightly used. At the same time, the renderer logs repeatedly emit worker_rpc_response_error errorMessage="Not a git repository" method=stable-metadata workerId=git. This continues after restarting the app and after resetting Codex app state.
bug-report-artifacts.tar.gz
What steps can reproduce the bug?
Uploaded thread: 019dac38-5275-7540-a26e-26250e368f5a
Open Codex Desktop on macOS.
Open or restore a normal Codex window/thread.
Let the app sit idle or use it lightly.
Open Activity Monitor.
Observe that there are 3 Codex Helper (Renderer) processes and that 2 of them stay above 100% CPU.
Check the Codex logs under ~/Library/Logs/com.openai.codex/ and observe repeated stable-metadata / Not a git repository errors.
What is the expected behavior?
Codex Desktop should not keep multiple renderer processes pinned above 100% CPU when only one window is open and the app is idle or lightly used. Git metadata checks should fail gracefully without creating a high-volume renderer error loop or sustained CPU usage.
Additional information
I already tried multiple local fixes and the issue still reproduces:
~/Library/Application Support/Codex~/Library/Application Support/com.openai.chatoriginconfig, and localorigin/main/origin/HEADrefs to those scratch reposNone of those steps fixed the problem.
Environment:
26.417.41555185841.2.026.5 (25F5058e)arm64Most recent observed process state:
118%to131%CPURelevant log pattern:
worker_rpc_response_error errorMessage="Not a git repository" method=stable-metadata workerId=gitIn one fresh restart log, I counted
22,894occurrences of that error.Related issues that may be relevant:
#18545(macOS renderer / WindowServer CPU)#18515(stable-metadata git log loop, VS Code extension)