feat: support sequential parallel tool calls #382
Draft
Conversation
This file contains hidden or 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
andreitava-uip
force-pushed
the
feat/fake-parallel-tools
branch
from
517f520 to
946a12c
Compare
andreitava-uip
force-pushed
the
feat/fake-parallel-tools
branch
from
946a12c to
b94a0c2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Added support for parallel tool calls, by executing them sequentially.
This is achieved via an orchestrator node (name subject to change if we decide it's confusing due to similarity with Orchestrator service) responsible for keeping track of the current tool call and incrementing.
The conditional edge can then route to the correct tool node based on the tool call index.
Also fixed tool call filtering. It now modifies to state to completely erase the filtered system tool calls.