-
Notifications
You must be signed in to change notification settings - Fork 2.6k
check if transfer target is a sibling agent #3862
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @AriYusa, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an inconsistency in the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
Response from ADK Triaging Agent Hello @AriYusa, thank you for creating this PR! This is a great fix and the testing plan is very clear. To help reviewers better understand the result of the manual E2E test, could you please provide a screenshot of the error that is raised in This information will help reviewers to review your PR more efficiently. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request correctly adds a check to prevent task transfers to sibling agents when disallow_transfer_to_peers is enabled. The implementation is straightforward and includes relevant unit tests. I've added one suggestion to refine the logic to correctly handle self-transfers, which should not be considered a transfer to a peer.
|
Hi @thank you for your contribution! We appreciate you taking the time to submit this pull request. |
Link to Issue or Description of Change
1. Link to an existing issue (if applicable):
Problem:
disallow_transfer_to_peers=Trueonly affected the instruction prompt. Subagents could still transfer tasks directly to sibling agents by inferring their names from conversation history or the user’s prompt.Solution:
Added a check in
_get_agent_to_run. Whendisallow_transfer_to_peers=True, the function now raises an error if a transfer to a sibling agent is attempted. I placed the check here because_get_agent_to_runalready contains a closely related validation for transfers to non-existent agents.Testing Plan
Unit Tests:
Manual End-to-End (E2E) Tests:
Manually tested before and after fix with
adk webby prompting subagents to transfer directly to sibling and getting newly added error after fixChecklist
Any dependent changes have been merged and published in downstream modules.(not applicable)