QuestionQ18

VerifiedDeveloping custom agents

You are designing a multiagent workflow with Agent Development Kit (ADK) on Agent Runtime that includes an orchestrator agent and an interactive claim adjuster agent. The claim adjuster agent is currently implemented as an agent-as-a-tool, but it treats turns as isolated requests, loses conversation history, and cannot hand control back to the orchestrator agent.

You need to rearchitect the coordination pattern so that the claim adjuster maintains stateful multiturn history, accesses shared context, and supports fluid, bidirectional handoffs.

What should you do?

Explanation

A hierarchical ADK subagent can share session state with the orchestrator and participate in model-driven delegation, allowing control to move between agents rather than treating the adjuster as an isolated tool call. A session service preserves conversation events and state across turns. These capabilities support the required shared context, multiturn history, and bidirectional handoffs. (cloud.google.com)

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!