/review at times looks at older, stale (already committed) changes

What version of Codex is running?

0.48.0-alpha.4

What subscription do you have?

Pro

Which model were you using?

gpt-5-codex-high

What platform is your computer?

macOS

What issue are you seeing?

Our project's root is a git repo with no code, and then several git submodules, each representing separate apps / extensions / dependencies.

Sometimes this confuses codex, it ends up looking at the wrong changes.

What steps can reproduce the bug?

Uploaded thread: 019a140b-0ccd-7b01-ac57-b8d1df9e866f

• Codex made some changes
• I run /review with Review uncommitted changes
• It correctly performs a review on the changed files within a sub-module and points out an issue
• Codex then fixes the issue, I notice there are some other issues with the changes, ask a few questions and make it perform further changes
• Run /review with Review uncommitted changes again - only this time it picks some completely random 'changes' which don't even exist, those were committed and pushed hours ago. Completely misses the only two uncommitted files in a sub-module out of the dozens of sub-modules we have

What is the expected behavior?

It should be able to figure out what's uncommitted.

I end up always performing a 'custom instructions' review, drag and drop the file paths and ask it to review these only. Then 'Review uncommitted changes' does the wrong thing majority of the times I've tried it, finally decided to report this as a bug.

Additional information

_No response_