openai / openai/codex

[macOS][Codex Desktop] Completed sub-agents remain under Running until opened

Open
#38,533 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug subagent
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using?

ChatGPT/Codex Desktop 26.810.41047 (build 6570)
Codex app-server 0.148.0-alpha.9

Platform

macOS 26.6.1 (25G76), arm64

What issue are you seeing?

Completed sub-agents remain listed under Running.

Opening one of those sub-agents shows that it has already stopped/completed. After returning to the sub-agent list, that same agent finally moves into Done.

This makes the running-agent count unreliable and makes it difficult to tell whether work is genuinely still active.

Steps to reproduce
  1. Start several sub-agents in one chat.
  2. Allow one or more sub-agents to complete.
  3. Open the sub-agent list.
  4. Observe that completed agents are still under Running.
  5. Open one of those agents. Its detail view shows it has stopped/completed.
  6. Return to the list. It now moves to Done.
Expected behavior

The list should move a sub-agent to Done as soon as its turn completes, without requiring the user to open that agent.

Diagnostic clue

The local desktop log records:

  • collab_hydration initially failing because a newly created rollout is temporarily empty.
  • Later turn/started and turn/completed events being received for an unknown conversation.

This suggests a possible hydration/state-registration race: after the initial empty-rollout failure, the conversation may not be registered, so later lifecycle events are discarded. Opening the child appears to force a fresh read and reconcile the displayed state.

Potential handling options could be retrying hydration after an empty rollout or buffering lifecycle events until the conversation is registered.

A short screen recording showing the deterministic UI sequence will be added in a follow-up comment.

Related reports

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the macOS sequence and examining desktop logs for collab_hydration, turn/started, and turn/completed events, especially the unknown-conversation messages. Trace how sub-agent lifecycle events update the Running and Done lists; done means completed agents move to Done without being opened.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.