-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Only 1 handoff getting called no matter what #771
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
Comments
I have also faced similar while creating a demo use case for shoe store and have some observations regarding this. I have attached the code snippet of the main/orchestrator agent where all the handoffs are occurring. The Main/Orchestrator Agent:
Main function to debug actions performed:
I have observed the following during my implementation and then had to switch to
I will edit this comment more if I found any other notable observations worthwhile to mention. |
Uh oh!
There was an error while loading. Please reload this page.
Please read this first
Describe the bug
I have an agent setup where I have an orchestrator that should call both handoff agents.
However, from what I can tell only the content generation agent is being called. Not only that but the final response being returned by the orchestrator agent is the response from the handoff agent
Here is my basic code
I know people have suggested converting them to tool calls. But why? Does that not defeat the point of handoff?
LASTLY:
Am I not allowed to use dict[str, Any] as part of an "output_type" field?
class TestOutput(BaseModel):
slides: list[dict[str, Any]]
^^I get an error when I do this.
Debug information
Repro steps
I think you can reproduce using the above example
Expected behavior
I would expect with all of my prompting that both agents get called. But I am just getting the output of the content generation agent and it is not handing off to anyone else. The output is also incorrect. And when I set the output type I get an error because I can't give an ambiguous object dict[str, Any]
The text was updated successfully, but these errors were encountered: