Update message_generator for multi-agent workflows #150
+6
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey @TaurusLondon thanks for raising this, I didn’t see the Command launch until now. Can you describe in more detail and/or give some example agent code where using Commands breaks the message_generator logic? It wasn’t immediately obvious to me, so it would help with validating this PR. Thank you! |
|
I did a more robust fix in #159 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When building multi-agent workflows, an event can be a Command to navigate among agents and it will break the message_generator method.
May need to use the latest version of langgraph (e.g. 0.2.66)