Codex App: side conversation shows already-applied edits as pending Accept/Reject diffs
Summary
After a file edit has already been applied to the workspace, Codex App can still show that edit in the side pane as a pending before/after diff with Accept and Reject actions.
This makes it unclear whether the change is already written, still pending review, or could be reverted by the displayed action.
Steps to reproduce
- In a main Codex task, ask the agent to edit a workspace file.
- Confirm that the agent reports the edit completed and that the file contains the updated text.
- Start a side conversation with
/side. - Inspect the side pane.
Actual behavior
The side pane displays the already-applied file change as a before/after diff and still offers Accept or Reject.
The side conversation did not create a new pending edit for that file.
Expected behavior
The App should synchronize the side-pane review state with the actual workspace state.
For an edit that is already applied:
- it should not be displayed as a pending Accept/Reject proposal; or
- it should be clearly labelled as historical/applied, with no action that could be mistaken for review approval or rollback.
Impact
This undermines confidence in the editing workflow: users cannot tell whether a change is final, pending, or at risk of being reverted. It is especially confusing in long-running tasks where side conversations are used for questions or review.
Related issue
This may be related to #13721, which reports that the Codex App review/diff pane can diverge from the actual Git working-tree state:
https://github.com/openai/codex/issues/13721
Environment
- Codex App version: [optional]
- Platform: [optional]