Review tab gets stuck on "Loading diff" on Windows because Codex App passes /F:/... as a literal path to git diff
What version of the Codex App are you using (From “About Codex” dialog)?
26.409.20454
What subscription do you have?
pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
In the Codex desktop app on Windows, the Review tab gets stuck on Loading diff for a normal text file and never renders the diff.
I reproduced this with a newly created dummy.txt containing a single line of plain text. The file appears in the changed files list and is clickable, but the diff pane stays on Loading diff forever.
This does not appear to be a Git or file-content problem. Git returns the expected diff immediately when run directly.
From the Codex desktop logs, the app appears to call Git with a literal path like /F:/HogeProject/Test/dummy.txt. That is important because this is not just a shell rendering issue. The logs show it in the argument list passed to Git.
That literal path appears to be invalid for git.exe on Windows and causes Git to fail with exit code 128, which appears to leave the Review pane stuck.
<img width="530" height="181" alt="Image" src="https://github.com/user-attachments/assets/85984d36-7940-47a6-92b9-c4f79f93bd81" />
What steps can reproduce the bug?
- Open Codex App on Windows
- Open a Git workspace
- Create a new text file such as dummy.txt
- Add one line of text
- Stage the file
- Open the Review tab
- Click the file in the changed files list
- Observe that the pane stays on Loading diff
I also tried:
- unstaging and restaging the file
- changing the integrated terminal shell to Git Bash
- restarting / reopening the app
- None of these fixed the issue.
What is the expected behavior?
The Review tab should render the text diff normally.
Additional information
Project root: F:/HogeProject/Test Git root: F:/HogeProject/Test
The file was a plain UTF-8 text file, not binary.
Example contents: これは Review 表示確認用のダミーテキストです
Git sees the file as normal text.
Command: git check-attr --all -- dummy.txt
Output:
diff --git a/dummy.txt b/dummy.txt
new file mode 100644
index 0000000..xxxxxxxx
--- /dev/null
+++ b/dummy.txt
@@ -0,0 +1 @@
+これは Review 表示確認用のダミーテキストです
I also reproduced the suspected root cause directly outside the app.
This fails when Git is called directly from PowerShell:
Command: git diff --cached -- /F:/HogeProject/Test/dummy.txt
Error: fatal: Invalid path '/F:': No such file or directory
These succeed:
git diff --cached -- F:/HogeProject/Test/dummy.txt
git diff --cached -- dummy.txt
I also verified that using Git Bash does not fix the Codex App Review issue, which suggests the problem is in Codex App's internal Git invocation rather than the integrated terminal setting.
From the Codex desktop log, Review appears to repeatedly run a command equivalent to git diff --cached -- /F:/HogeProject/Test/dummy.txtand gets exitCode=128.
So this looks like a Windows path normalization bug in Codex App's diff/review flow. The key point is that /F:/... appears to be passed as a literal Git argument, and reproducing that exact argument outside the app fails, while the same command succeeds with F:/....
16 Comments
I have the same issue on Windows, and I checked the local Codex desktop logs on this machine before commenting.
The logs show the Review flow repeatedly invoking Git with a literal Windows path prefixed as
/C:/..., for example:git diff --no-ext-diff --no-textconv --color=never --src-prefix=a/ --dst-prefix=b/ -- /C:/Users/FlemmingBK/repo/bc-agentic-dev-tools-marketplace/plugins/al-build/.codex-plugin/plugin.jsonThose calls are failing with
exitCode=128in the app logs.I also ran the equivalent command directly with
git.exein the same repo, and it fails the same way:fatal: Invalid path '/C:': No such file or directorySo this looks consistent with the root cause described here: the app appears to be passing
/C:/...as a literal Git path on Windows, which leaves the Review diff stuck loading.Possible extra signal from the same log set: I also saw other Windows path-handling warnings in the app around workspace/worktree resolution, including
ENOENTentries for/mnt/c/...and\\?\\C:\...paths.I'm having the same issue, this is an important one, it's happening since last codex update
Having the same problem here in Korea
Same issue here
Same problem since updating yesterday
Same problem, I have Codex 26.409.20454
Same problem
Same problem
Same problem (russia)
Commit your changes : Stuck, saying Loading diff.. / No changes to commit.
Same, hope it gets fixed soon
same problem,and at this time, the CPU usage will spike
same problem
Thanks for the bug reports. We're working on a fix, and it should be ready for the next release.
@etraut-openai just FYI this seems to be happening for WSL users as well.
@etraut-openai
Confirmed that the loading diff issue is fixed in version 26.415.20818. Thanks for fixing this !