Repository navigation
Description
** Please make sure you read the contribution guide and file the issues in the right place. **
Contribution guide.
Is your feature request related to a problem? Please describe.
Yes, this request addresses a significant User Experience (UX) and latency issue when implementing Hierarchical Multi-Agent systems using the AgentTool pattern.
Currently, when a Parent Agent delegates a task to a Sub-agent wrapped in an AgentTool, the execution acts as a "black box" or a blocking operation.
The Parent Agent invokes the AgentTool.
The Sub-agent starts running (which may involve its own chain of thought, tool calls, and retries).
The Problem: During the Sub-agent's execution, no events are yielded to the main Runner. The application receives no feedback (no partial text, no tool call notifications) until the Sub-agent completes its entire lifecycle and returns the final string result.
If a sub-agent takes 30 seconds to complete a complex task, the frontend application appears unresponsive for 30 seconds. The developer loses visibility into the intermediate_data and intermediate_responses of the sub-agent in real-time.
Describe the solution you'd like
I would like AgentTool (and the underlying Runner logic) to support event bubbling or streaming propagation.
When an AgentTool is executed:
It should utilize the Sub-agent's run_async iterator.
It should intercept events generated by the Sub-agent (including model chunks, inner tool_calls, and tool_responses).
These events should be yielded up to the parent Runner immediately, rather than buffered until completion.
This would allow the frontend application (e.g., via adk run_sse) to display the Sub-agent's progress (e.g., "Sub-agent is searching Google...", "Sub-agent is writing code...") in real-time, maintaining a responsive UI.
Describe alternatives you've considered
Custom Orchestrator Agent: Manually implementing a custom agent class inheriting from BaseAgent and overriding _run_async_impl. Inside this manual implementation, I can call the sub-agent's run_async and manually yield the events. This works but requires significant boilerplate code and defeats the convenience of using the standard AgentTool wrapper.
Additional context
This is critical for "Coordinator -> Sub-agent" architectures.
Current behavior: Runner yields events for the Coordinator -> Silence for 20s (while Sub-agent works) -> Runner yields final answer.
Desired behavior: Runner yields Coordinator events -> Runner yields Sub-agent thought process/tool events -> Runner yields final answer.
This feature would significantly improve the usability of ADK for complex, long-running agentic workflows.
Activity
feat(agent-tool): Add event streaming propagation from AgentTool sub-…
feat(agent-tool): Add event streaming propagation from AgentTool sub-…
klateefa commentedon Feb 11, 2026
@abhinav-rafa Thank you for submitting this feature request. It’s currently under review by our team, and I’ll keep you posted on any updates. We appreciate your input!
CS-PK commentedon Mar 23, 2026
Strong +1 from production use case.
We run a multi-agent orchestrator where sub-agents are wrapped as AgentTool and also called remotely via A2A. We needed real-time progress updates in the UI ("Searching feeds...",
"Resolving labels 3/10") while sub-agent tools execute.
Because AgentTool.run_async() consumes all events internally (only keeps last_content), we had to build a parallel transport:
execution
This works but is fragile — we're maintaining a copy of ADK's /run_sse event serialization logic, and any ADK update to that endpoint could silently break us.
What would solve this cleanly:
Any of these would eliminate our /run_sse override entirely.
DeanChensj commentedon Jul 22, 2026
Thank you for bringing this up! This feature request is already supported via the Single-Turn Sub-Agent pattern, which is the recommended way to compose agents in ADK 2.0.
Instead of wrapping your sub-agent with
AgentTool, you should setmode=""single_turn""on the sub-agent and pass it directly to the parent'ssub_agentslist:Why this works:
Under the hood,
single_turnsub-agents are executed inline by the parent agent's runner rather than starting a separate isolated runner. This allows all intermediate events (thoughts, inner tool calls, tool responses) to automatically bubble up and be streamed to your client application in real-time, solving the unresponsive UI/latency issue.For more details on how to set this up, please check the Single-Turn Mode Guide and the Single-Turn Sub-Agent Sample.
adk-bot commentedon Jul 29, 2026
This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.
adk-bot commentedon Aug 6, 2026
This has been automatically closed because it has been marked as stale for over 7 days.