You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Show subagent start time and execution duration #42564
It would be very useful to display timing information for subagent calls in the UI.
Currently, when multiple subagents are invoked, it can be difficult to understand when each subagent was started and how long it took to complete, especially when several agents are running or being delegated in sequence.
Proposed enhancement
For each subagent invocation, display:
Invocation time — when the subagent was started.
Execution duration — how long the subagent took to complete.
Optionally, completion time as well, if it fits naturally into the existing UI.
For example, the UI could show something similar to:
▣ Delegators/Workers/Openai-Gpt-5.6-Luna/... 15:02:31
Completed in 42s
▣ General 15:03:14
Completed in 18s
▣ Code-Reviewers/Openai-Gpt-5.6-Luna/... 15:03:35
Completed in 1m 07s
This would make it much easier to understand the execution flow, identify slow subagents, and debug or analyze complex multi-agent workflows.
Why this would be useful
This information would help with:
understanding the timeline of agent/subagent execution;
identifying slow or unexpectedly long-running subagents;
debugging delegation and parallel execution;
comparing execution times between different agents;
getting a clearer picture of overall workflow performance.
The timestamp could be displayed inline with the subagent call, while the duration could be added once the subagent finishes.
Example
I think even a minimal implementation showing the start time + execution duration would already provide a lot of value.
I agree that #27995 covers the broader Agent Activity Panel use case, and that it already mentions start time and elapsed duration in the agent detail view.
The specific part I wanted to highlight with this issue is the inline/persistent display of timing information directly in the main conversation/task history, as shown in the attached mockup.
The distinction I'm thinking of is:
#27995 → a live sidebar for monitoring background agents and viewing their current state/output. #42564 → keeping the start time and execution duration visible next to the subagent invocation itself, so the execution timeline remains understandable after the workflow has completed.
For example:
▣ Delegators/Workers/...
Started at 15:02:31 · Completed in 42s
▣ General
Started at 15:03:14 · Completed in 18s
This would make it easy to see which subagents were started when and which ones consumed the most time without having to open a separate activity view.
If this is considered part of the intended implementation of #27995, I'm happy for this issue to be treated as a duplicate. I mainly wanted to make sure this particular UX aspect isn't lost.
Activity
github-actions commentedon Aug 14, 2026
This issue might be a duplicate of existing issues. Please check:
started_at,ended_at, andduration_ms— very similar scopeNESTOWL commentedon Aug 14, 2026
Thanks for pointing out the related issues.
I agree that #27995 covers the broader Agent Activity Panel use case, and that it already mentions start time and elapsed duration in the agent detail view.
The specific part I wanted to highlight with this issue is the inline/persistent display of timing information directly in the main conversation/task history, as shown in the attached mockup.
The distinction I'm thinking of is:
#27995 → a live sidebar for monitoring background agents and viewing their current state/output.
#42564 → keeping the start time and execution duration visible next to the subagent invocation itself, so the execution timeline remains understandable after the workflow has completed.
For example:
▣ Delegators/Workers/...
Started at 15:02:31 · Completed in 42s
▣ General
Started at 15:03:14 · Completed in 18s
This would make it easy to see which subagents were started when and which ones consumed the most time without having to open a separate activity view.
If this is considered part of the intended implementation of #27995, I'm happy for this issue to be treated as a duplicate. I mainly wanted to make sure this particular UX aspect isn't lost.
NESTOWL commentedon Aug 14, 2026
I also think we should display the date. It’s really inconvenient when you don’t know what day the request was made.

github-actions commentedon Oct 15, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.