Repository navigation
[FEATURE]: expose execution metadata for tool/subagent runs to the agent #23474
Description
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Please expose minimal execution metadata for tool calls and subagent/task runs to the active agent.
Right now OpenCode clearly has session/message/event data, but the agent still cannot reliably answer questions like:
- did the task stop in the middle?
- is it still running or just slow?
- when was the last successful activity?
- did it fail, timeout, or get cancelled?
A small structured timeline would be enough. For example:
idkind(tool_callorsubagent_run)namestatusstarted_atended_atduration_mslast_activity_atparent_iderror_summary
The main gap is agent visibility, not just UI.
A UI timeline would help humans, but agent-visible metadata would let the agent:
- distinguish slow vs stuck
- decide whether to retry or wait
- explain interruptions precisely
- summarize partial runs without guessing
Related issues seem narrower or UI-specific:
- ACP: tool_call_update in_progress notifications don't include tool metadata #14592 is about ACP
tool_call_updatemetadata duringin_progress - Task child session can exist without metadata.sessionId after interruption, leaving web UI unable to show subagent activity #22348 is about missing
metadata.sessionIdafter interruption - [FEATURE] Add real-time call trace visualization for debugging multi-agent workflows #20168 is about real-time trace visualization
This request is broader: expose a minimal execution timeline/metadata surface that the agent itself can inspect across tool calls and subagent runs.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Apr 20, 2026
This issue might be a duplicate of existing issues. Please check:
id,kind,status,started_at,ended_at,duration_ms, etc.) and the same motivation (agent visibility gap). That issue was closed; please check why it was closed before proceeding.If you believe this is a distinct request, please clarify what is different from #23421.
jjangga0214 commentedon Apr 20, 2026
This is intended as the replacement for #23421, not a distinct feature request.
#23421 was auto-closed because I did not use the required feature-request title/template format in time. This issue is the same request reposted in the required format so it can be triaged normally.
I also left a pointer on #23421 to redirect here.
github-actions commentedon Jul 7, 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.