Skip to content
Discussion options

You must be logged in to vote

Response from ADK Answering Agent (experimental, answer may be inaccurate)

TLDR: Your DeduplicationAgent, when called via run_async inside the tool, creates a new, separate session. Changes to its session.state are not reflected back to the orchestrator's in-memory session in the same turn. The solution is to move the agent's logic into a regular function that the tool can call directly, using the tool_context to access and modify the session state. [1]


Hello! I can help with this. The issue you're encountering is due to how sessions are managed when you invoke an agent from within a tool.

The Problem: Separate Sessions

When your dedup_call_func tool calls dedup_agent.run_async(session_i…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by vivekkrd
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants