bug: review pane loses previous changes after adding a nested git repo

Open 💬 2 comments Opened Apr 16, 2026 by DDDOH
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.409.20454 (1462)

What subscription do you have?

pro

What platform is your computer?

macOS 26.4.1 (25E253)

What issue are you seeing?

After adding a nested Git repository inside an existing workspace repository, the Codex Review pane no longer shows the previous round of changes reliably.

In particular, the “上一轮更改” / “Previous changes” section becomes empty, even though changes were made in the prior round. The UI shows a message equivalent to “file changes will appear here or the latest diff is no longer available”.

This seems related to the review pane binding itself to the currently active Git context once a nested repo exists.

What steps can reproduce the bug?

  1. Open a Git repository in Codex / VS Code.
  2. Work for a few rounds so that the Review pane shows previous changes normally.
  3. Initialize a nested Git repository inside a subdirectory of the outer repo.
  4. Continue working in the same overall workspace.
  5. Open the Review pane and check “Previous changes”.

What is the expected behavior?

The Review pane should still be able to show the previous round of changes, or at minimum make it clear which repository context it is using.

Nested repositories should not silently make the previous diff disappear.

Additional information

  • Outer repo: monorepo
  • Inner repo: nested Git repo used for a formalization artifact
  • Source Control can detect both repos, but the Review pane appears to lose the previous diff context
  • This may be a repo-context selection issue rather than a raw Git detection issue

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #17851
  • #17963

Powered by Codex Action

DDDOH · 4 months ago

Both #17851 and #17963 are different from my case. My case is specific to nested git repo.

Potential duplicates detected. Please review them and close your issue if it is a duplicate. Diffs outside of Last Turn no longer visible in review panel #17851 Review panel "Last turn" does not show all files updated in the last turn #17963 _Powered by Codex Action_