Update FlowManager to support role and task messages #68
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
…sing happens in set_node, update examples
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
aconchillo
reviewed
Dec 20, 2024
aconchillo
approved these changes
Dec 20, 2024
|
Awesome! LGTM! |
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.
Flows code
Changed
Nodes now have two message types to better delineate defining the role or
persona of the bot from the task it needs to accomplish. The message types are:
role_message, which defines the personality or role of the bottask_message, which defines the task to be completed for a given noderole_messagescan be defined for the initial node and then inherited bysubsequent nodes. You can treat this as an LLM "system" message.
Simplified FlowManager initialization by removing the need for manual context
setup in both static and dynamic flows. Now, you need to create a
FlowManagerand initialize it to start the flow.
All examples have been updated to align with the API changes.
Flows editor
Also, the Flow Editor needed to be updated for the new message structure as well. This PR includes an update there, as well as updates to all editor JSON examples.