Draft prepared with Codex assistance; details verified by me.
I searched existing issues first. The closest matches I found were #13689 and #14182, but neither seemed to fully cover this specific Summary-tab failure mode.
What version of the Codex App are you using (From “About Codex” dialog)?
Version shown in the About Codex screen:
26.409.61251
I also observed the Windows Store package path:
OpenAI.Codex_26.409.7971.0_x64__2p2nqsd0c76g0
Rollout/session metadata on this machine also shows:
cli_version: 0.119.0-alpha.28
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows host with a WSL workspace
What issue are you seeing?
In the Windows Codex desktop app, the Summary tab in the right-hand panel shows misleading GitHub/PR status errors for a valid WSL-hosted Git repo.
The messages include:
GitHub CLI unavailable
Pull request status unavailable
However, GitHub CLI is not actually unavailable.
What I verified:
- Linux
gh in WSL works
- Windows
gh.exe works
gh auth status succeeds
- after adding the repo as a Windows Git
safe.directory, Windows gh.exe repo view and gh.exe pr status also worked normally against the checkout
So the Summary tab message appears to be a generic fallback rather than a literal statement that gh is missing.
What steps can reproduce the bug?
- Use the Codex Windows desktop app with a repo hosted in WSL, for example
/home/...
- Open a thread for that repo
- Open the Summary tab on the right-hand side
- Observe
GitHub CLI unavailable or Pull request status unavailable
What is the expected behaviour?
The Summary tab should correctly detect GitHub/PR state for the repo, or at least show a specific error that reflects the real failure.
It should not claim GitHub CLI is unavailable when gh is installed, authenticated, and working.
What is the actual behaviour?
The Summary tab shows misleading GitHub/PR status messages even though GitHub CLI works in both WSL and Windows contexts.
Additional information
I ruled out several simpler explanations:
- Windows Git
safe.directory trust was initially missing for the WSL checkout, but fixing that did not fix the Summary tab.
- I also found and repaired a separate local SQLite state DB issue (
state_5.sqlite migration mismatch). That fixed thread metadata updates, but the Summary tab problem still remained.
The strongest evidence now points to a WSL git-path watcher problem in the desktop app itself.
In the desktop logs, the app’s git repo watcher fails with ENOENT on WSL .git paths such as:
/home/<redacted>/projects/codex/.git/HEAD
/home/<redacted>/projects/codex/.git/FETCH_HEAD
/home/<redacted>/projects/codex/.git/packed-refs
Related git commands are then aborted before start.
So this looks less like a real gh problem and more like a Windows desktop app bug in WSL git-path watching / repo-state detection.
Potentially related issues:
Draft prepared with Codex assistance; details verified by me.
I searched existing issues first. The closest matches I found were #13689 and #14182, but neither seemed to fully cover this specific Summary-tab failure mode.
What version of the Codex App are you using (From “About Codex” dialog)?
Version shown in the About Codex screen:
26.409.61251I also observed the Windows Store package path:
OpenAI.Codex_26.409.7971.0_x64__2p2nqsd0c76g0Rollout/session metadata on this machine also shows:
cli_version: 0.119.0-alpha.28What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows host with a WSL workspace
What issue are you seeing?
In the Windows Codex desktop app, the Summary tab in the right-hand panel shows misleading GitHub/PR status errors for a valid WSL-hosted Git repo.
The messages include:
GitHub CLI unavailablePull request status unavailableHowever, GitHub CLI is not actually unavailable.
What I verified:
ghin WSL worksgh.exeworksgh auth statussucceedssafe.directory, Windowsgh.exe repo viewandgh.exe pr statusalso worked normally against the checkoutSo the Summary tab message appears to be a generic fallback rather than a literal statement that
ghis missing.What steps can reproduce the bug?
/home/...GitHub CLI unavailableorPull request status unavailableWhat is the expected behaviour?
The Summary tab should correctly detect GitHub/PR state for the repo, or at least show a specific error that reflects the real failure.
It should not claim GitHub CLI is unavailable when
ghis installed, authenticated, and working.What is the actual behaviour?
The Summary tab shows misleading GitHub/PR status messages even though GitHub CLI works in both WSL and Windows contexts.
Additional information
I ruled out several simpler explanations:
safe.directorytrust was initially missing for the WSL checkout, but fixing that did not fix the Summary tab.state_5.sqlitemigration mismatch). That fixed thread metadata updates, but the Summary tab problem still remained.The strongest evidence now points to a WSL git-path watcher problem in the desktop app itself.
In the desktop logs, the app’s git repo watcher fails with
ENOENTon WSL.gitpaths such as:/home/<redacted>/projects/codex/.git/HEAD/home/<redacted>/projects/codex/.git/FETCH_HEAD/home/<redacted>/projects/codex/.git/packed-refsRelated git commands are then aborted before start.
So this looks less like a real
ghproblem and more like a Windows desktop app bug in WSL git-path watching / repo-state detection.Potentially related issues:
GitHub CLI is not installedmessage