Codex Desktop: “Edited – Review” reports 13 files while task changes span 34 files
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Environment
Codex desktop app on macOS.
Version information reported by the user from the app:
Powered by Codex & OWL Version 26.903.61454 Released Sep 9, 2026
Observed behavior
After a single-agent coding task, the user reported that the “Edited – Review” UI showed 13 edited files. A subsequent Git inspection of the same working directory showed:
- 22 modified tracked files
- 12 new untracked files
- 34 files total
- 1,514 added lines (including new files) and 536 deleted lines
The working tree was clean before implementation. The task used both apply_patch and shell-executed Python/Node scripts to make edits. No subagents were used. The implementation occurred in one assistant turn after an earlier turn that only investigated and requested boundary authorization.
The agent verified the Git counts, but could not inspect the review UI directly or capture a screenshot. The 13-file UI count is the user's observation. The cause is not established: please investigate whether script-based changes, untracked files, or the scope of the edited-files card explain the mismatch.
Reproduction to investigate
- Start a task in a clean Git working tree in Codex Desktop.
- Have the agent modify tracked files and add new files using a mixture of apply_patch and shell-executed scripts, within the same implementation turn.
- After completion, compare the “Edited N files / Review” card and its file list with
git status --short,git diff --name-only, andgit ls-files --others --exclude-standard. - Check whether all task-created and task-modified files appear, and whether the selected review scope is clearly indicated.
Expected behavior
The task's edited-files card and associated review should account for all edits made by that task regardless of editing mechanism, including new untracked files. If the card intentionally covers only a subset, that scope should be explicit so users do not mistake it for the complete task change-set.
Impact
An apparently complete review summary can cause users to miss changes when reviewing the agent's work. This is also a reporting failure by the agent: it should reconcile its final change inventory against Git instead of treating the displayed count as authoritative.
Related report
Related symptom: #36219 concerns omitted subagent changes. This occurrence used no subagents and may have a different cause.
No private repository names, source code, session transcripts, or logs are included.
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 Codex Desktop “Edited–Review” card and its file list, then reproduce the mixed apply_patch and shell-script workflow in a clean working tree. Compare the displayed scope with git status --short, git diff --name-only, and git ls-files --others --exclude-standard; done means all task-created changes are represented or the card’s narrower scope is explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, macos
- Domain
- desktop, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100