[TUI] Inline apply_patch diffs disappear after codex resume even though FileChange events persist
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
codex-cli 0.152.0
What subscription do you have?
Plus
Which model were you using?
No response
What platform is your computer?
Linux 6.18.33.2-microsoft-standard-WSL2 x86_64 unknown
What terminal emulator and version are you using (if applicable)?
No response
Codex doctor report
What issue are you seeing?
After resuming a session, historical FileChange inline diff is not rendered.
The rollout JSONL still contains the FileChange event and unified_diff.
The workspace is not a Git repository, but the diff rendered correctly before resume.
What steps can reproduce the bug?
Uploaded thread: 01a05f0a-6f7a-7c51-bd37-05682092f78c
What is the expected behavior?
After resuming a session, historical FileChange inline diff should be rendered.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the uploaded thread and inspect the rollout JSONL for the persisted FileChange event and unified_diff, then trace how the TUI renders that history before and after resume. Done means the historical inline diff renders after resume in a non-Git workspace, while the existing FileChange data remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100