[macOS] Subagent’s execution status once it has provided its final response
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.803.41515
What subscription do you have?
Pro
What platform is your computer?
MacOS
What issue are you seeing?
019fbe75-4cba-79c2-9651-2968f2f0e8e5
When using Ultra Mode, the artificial intelligence will create sub-agents that it will use to complete the requested task. The problem is that most of the time, these sub-agents are shown as running when they aren’t, causing some projects. shows 45 agents running and others 165, when in reality, if you inspect the conversations one by one, you’ll realize that most are inactive and that only two or three are actually in progress. This is an issue with the Codex app, which fails to update a subagent’s execution status once it has provided its final response.
What steps can reproduce the bug?
Use Ultra
What is the expected behavior?
No response
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
Reproduce the issue in the macOS Codex app by using Ultra Mode and observing subagent statuses after they provide their final responses. Investigate the execution-status handling for subagents; done means inactive subagents no longer remain marked as running while only active work is counted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100