[Codex App] Completed subagents remain running and their timers keep increasing until opened
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)?
Codex Desktop MSIX: 26.818.2441.0 (x64)
What subscription do you have?
chatGPT Pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
When a subagent finishes, its entry in the parent task's subagent list does not update to the completed state. It continues to appear as running/in progress, and its elapsed-time counter keeps increasing.
If I click and open the subagent, the UI refreshes and immediately shows the subagent as completed with its final result. This makes the live subagent list appear incorrect until the subagent is opened.
The completion appears to be persisted because the final state is shown after opening the subagent. I have not observed data loss; the problem is that the live list/status display is stale.
What steps can reproduce the bug?
- Start a task in Codex Desktop.
- Spawn a subagent and let it complete.
- Leave the completed subagent unopened and return to the parent task or subagent list.
- Observe that the subagent still appears to be running/in progress and that its elapsed-time counter continues to advance.
- Click/open the subagent.
- Observe that it now shows the completed state and final result.
What is the expected behavior?
As soon as a subagent completes, the parent task's subagent list should receive and display the completed status without requiring the user to open the subagent. The elapsed-time counter should stop at completion, and the row should not continue to appear active.
Additional information
This appears to be a live UI state-synchronization problem: opening the subagent forces a refresh that applies the already-persisted completion state.
This is related in symptom to #20754 (the Desktop UI can remain stuck showing a running state after a task has completed), but this report is specifically about completed subagents whose status and timer remain stale until the subagent is opened.
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 issue in Codex Desktop and inspect the parent task's subagent list and its live status-update path. Verify that a completed subagent updates without being opened, that its elapsed timer stops, and that the final result remains visible after refresh.
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
- Mostly clear
- Newbie friendliness
- 55/100