Before submitting
Area
apps/web
Problem or use case
Hey hi guys,
Was wondering if like the codex app we can have the sub-agent level UI segmentation, T3 app should also show the sub agents being spawned, clicking each of them then should show the work they are doing and the file edits being performed.
Proposed solution
Each thread should then show the sub agents being spawned up, under itself.
Asked codex to generate a rough idea of it, so it might look like this, obvsly can be improved:
Why this matters
This matters because sub agent level UI segmentation is important, as end user i dont even know how many sub agents did the main thread spawned. So it is necessary to have this feature.
Smallest useful scope
Add expandable sub-agent threads beneath their parent thread in the existing left sidebar. Each child should show its name and current status (queued, working, completed, or failed). Selecting a child opens that agent’s existing thread/activity view in the main pane. No new orchestration controls or cross-agent messaging are required for the first release.
Alternatives considered
I use codex app as reference point, because it does show me the sub agents being spawned in UI.
Risks or tradeoffs
Nested threads add sidebar complexity, especially for deeply nested or numerous agents; the UI should keep hierarchy to one level initially and allow collapsing the parent. Status updates must stay synchronized with the underlying agent lifecycle, including agents that fail, stop, or finish while the app is closed. The initial version should reuse the existing thread/activity view rather than introducing a separate agent-inspection system.
Examples or references
Contribution
Before submitting
Area
apps/web
Problem or use case
Hey hi guys,
Was wondering if like the codex app we can have the sub-agent level UI segmentation, T3 app should also show the sub agents being spawned, clicking each of them then should show the work they are doing and the file edits being performed.
Proposed solution
Each thread should then show the sub agents being spawned up, under itself.
Asked codex to generate a rough idea of it, so it might look like this, obvsly can be improved:
Why this matters
This matters because sub agent level UI segmentation is important, as end user i dont even know how many sub agents did the main thread spawned. So it is necessary to have this feature.
Smallest useful scope
Add expandable sub-agent threads beneath their parent thread in the existing left sidebar. Each child should show its name and current status (queued, working, completed, or failed). Selecting a child opens that agent’s existing thread/activity view in the main pane. No new orchestration controls or cross-agent messaging are required for the first release.
Alternatives considered
I use codex app as reference point, because it does show me the sub agents being spawned in UI.
Risks or tradeoffs
Nested threads add sidebar complexity, especially for deeply nested or numerous agents; the UI should keep hierarchy to one level initially and allow collapsing the parent. Status updates must stay synchronized with the underlying agent lifecycle, including agents that fail, stop, or finish while the app is closed. The initial version should reuse the existing thread/activity view rather than introducing a separate agent-inspection system.
Examples or references
Contribution