Replies: 1 comment
-
Thank you for your feedback @sjavaheri. We're rethinking the Graph tool as part of #214. Both of your items here should be addressed in the revised implementation. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
👋 Hello. When using the strands multi agent graph tool, I was surprised by the implementation of each node. I was curious if these things are planned features in the future, or if they were avoided for a reason I am missing.
I expected that I would be able to pass in a predefined agent at each node, or at least configure an agent at each node to have certain tools. Was this planned for the future / avoided for a good reason?
I expected that a coordinator node in a hierarchical workflow could choose which other nodes to send its output too, so I was surprised to see that for any topology type, each node broadcasts its output to all its neighbours, with no selection. If this was by design, what does it achieve? I thought the point of the graph hierarchy was the coordinator node could make decisions on which agents to call when, similar to when a subset of agents are provided to a parent agent directly as tools.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions