Subagent activity is invisible from the main thread list, spinner only reflects main thread

What version of the Codex App are you using (From “About Codex” dialog)?

26.623.101652

What subscription do you have?

Pro

What platform is your computer?

Darwin 24.5.0 arm64 arm

What issue are you seeing?

Subagent activity is not visible from the main thread sidebar on the left of Codex App. That's a problem because I often switch around the main threads, and see active threads via the spinners and completed turns via the little blue dots. That tells me the thread is ready for my next input. But if that thread spun up one or more subagents, they may or may not still be working without main thread oversight. Then I cannot see if the thread as a whole is done with its tasks because the spinner may not be showing. The only way to see if everything is ready is to go in and check the subagents. Then the spinner/blue dot can be misleading.

I would consider making the spinner a dual-state visual, with the regular spinner for the main thread and possible a subagent-specific spinner for any work that's ongoing off the main thread.

What steps can reproduce the bug?

1. Set an orchestrator thread A to work, asking it to use subagents to complete certain tasks.
2. Switch to another main thread.
3. Subagent of thread A is still busy, main thread A completes its turn without active supervision of the subagent.
4. Thread A spinner is replaced by a blue dot - subagent is still working.

What is the expected behavior?

Show the activity of both the subagent and the main thread (better if distinct visuals) in the main thread sidebar for effective monitoring of completion across main threads and subagents.

Additional information

I don't think coupling the spinner to the subagent/main thread activity as an "OR" operand would be the right approach, because it can be useful to know if one or the other has completed at a glance. Perhaps an expandable list of subagents below the main thread would be ideal, using the same expansion UX as the Project -> Child thread expansion.