feat: supervisor should be configurable agent #68
Comments
This was referenced Dec 10, 2024
pkarw
added a commit
that referenced
this issue
Dec 12, 2024
…ve object (#105) Fixes #68 Related #102 There are a lot of changes in this PR, I will break them down here, together with motivation. The prime motivation for the change was to simplify the structure of "state" by getting rid of agent specific properties (such as agentName, agentRequest) and moving to a simple state object that can have "child" states (either single element, or an array). That way, we could get rid of special handling for supervisor, resource planner (two built-in agents) and further simplify the logic. Thanks to that, we have "out-of-the-box" support for parallelism, cancellations, hand-offs. If agent wants to delegate, simply create new `workflowState` and add it as a child, then return state (see how "supervisor" is implemented). If agent wants to hand-off the task, they can simply replace their entire state (see how "resourcePlanner" gets its job done). Other changes worth mentioning: - Agent does not have role anymore. Now, what matters is the key on "team" object. This is aligned with how we define tools. This will make it better and more future proof if we serialize state object on the server. We no longer rely on array positions. - Renamed "members" array to "team" object - Supervisor and Planner are now normal agents (and you can overwrite them, or change their behavior, or define your own) - Added tool helpers to be used on the server side Here is screenshot of what the output looks like at the moment:  --------- Co-authored-by: Piotr Karwatka <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should have its own prompt and customization
Should be special one for dealing with smaller tasks, not only complex workflows
Can have access to additional data to be better at planning
The text was updated successfully, but these errors were encountered: