Subagent/team UI not surfaced on resumed history threads #16358
Description
Summary
When resuming a Codex thread from history, subagents can still run and produce results, but the subagent/team UI is not surfaced to the user the way it is in a fresh/live thread. This makes it hard to understand what is happening during delegated work.
Expected behavior
If subagent activity is available for the thread, the Codex app should surface the active team/task state consistently, including on resumed threads, so the user can:
- see that subagents were spawned
- see which agents are working on which task
- inspect agent activity/results as work progresses
Actual behavior
In a resumed thread:
- subagents are active on the backend side
- delegated work still happens
- but the visible team/task UI is not exposed to the user
- from the user perspective, there is no clear indication that a team is running unless the assistant manually reports it in chat
Repro
- Start a thread in the Codex app where subagents/team activity is visible.
- Leave the thread and later resume it from history.
- Ask Codex to send a multi-agent team on a task.
- Observe that subagent work can still happen, but the visible team/task UI is missing or not surfaced as before.
Notes
- The distinguishing factor observed here was that the thread was resumed from history; the same project/task previously exposed visible team/task activity.
- Codex docs indicate subagent activity is surfaced in the Codex app/CLI, so the resumed-thread behavior appears inconsistent.
- This creates UX confusion because the user cannot tell what task delegation is active or what the agents are doing.
Impact
This makes team workflows much harder to trust/debug in resumed threads because the user loses visibility into:
- active delegated tasks
- agent ownership
- progress/results
Environment
- Codex app on Windows
- Thread resumed from history
- Multi-agent/subagent workflow active