[Windows][Desktop] Review comments for side-chat file changes are routed to the main chat
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.901.5280.0
What subscription do you have?
Plus
What platform is your computer?
Windows 25H2, build 26200.9168, x64
What issue are you seeing?
When a side chat modifies files, inline comments added from the Changes/review pane are routed to the main chat when requesting follow-up changes.
The comments should be sent to the side chat that produced and owns the file changes. Instead, they appear in and are handled by the main chat. This can interrupt the main task and leaves the side chat without the requested review feedback.
What steps can reproduce the bug?
- Open a task in Codex Desktop.
- Open a side chat.
- Ask the side chat to modify one or more files.
- Open the Changes/review pane for those modifications.
- Add one or more inline code comments.
- Request Codex to apply the commented changes.
- Observe that the comments/request are sent to the main chat instead of the side chat.
What is the expected behavior?
Review comments and the follow-up request should be routed to the side chat associated with the reviewed file changes.
Additional information
Related but apparently distinct from #40822, which concerns a failed /btw fork routing a prompt into the main turn in the TUI.
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 by reproducing the flow in Codex Desktop on Windows: create a side chat change, add an inline comment in the Changes/review pane, and request the follow-up. Trace how the review request selects a chat, then verify that comments and the follow-up are delivered to the side chat rather than the main chat.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100