Repository navigation
Support AuthenticatedAgentTool #2445
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.
I am trying to build Agent with ReAct planner that uses Agents as Tools. There is no concept of authenticated AgentTool yet AgentTool is run as totally separate session meaning it does not generate events for authentication (or it genrates but they are not passed to main runner). Tools quite often are very technical or blend business and technical params that agent need to collect. Abstracting google toolset tools as agent which clarifies defaults and add more clarification on how to properly use distinct endpoints is more efficient way to have functional agent. Problem is that there is no way to authorize agent to act on user behalf on systems covered by that subagents used as tools.
Describe the solution you'd like
AuthorizedAgentTool with auth_config where we specify credentials_key where token is located or auth_credentials and auth_Schema wit hdetails how parent agent configured to use AuthenticatedAgentTool should collect.
Describe alternatives you've considered
NA
Additional context
Add any other context or screenshots about the feature request here.
Activity
klateefa commentedon Nov 24, 2025
@bimission Thank you for reporting this. I understand the request is currently under review. Please keep me posted if anything else is needed. Thanks for your patience.
DeanChensj commentedon Oct 14, 2026
Thank you for raising this and for your patience!
Since this issue was opened,
AgentToolhas been updated to automatically forward the parent invocation'scredential_service(tool_context._invocation_context.credential_service) as well as non-internalsession.statekeys into the child agent's runner and propagate state updates back to the parent session. Additionally, if a sub-agent needs to trigger interactive multi-turn authentication prompts directly in the main conversation session, we recommend registering it viasub_agents=[...]so it runs inline in the parent's session.We are closing this issue for now, but if your authentication flow isn't covered by these mechanisms or you run into any issues, please feel free to open a new issue with your setup details!
github-actions commentedon Oct 14, 2026
Are you satisfied with the resolution of your issue?
Yes
No