-
Notifications
You must be signed in to change notification settings - Fork 2k
[WIP] React use dspy.ToolCalls
#8472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
chenmoneygithub
wants to merge
21
commits into
stanfordnlp:main
Choose a base branch
from
chenmoneygithub:react-native-tool-calling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[WIP] React use dspy.ToolCalls
#8472
chenmoneygithub
wants to merge
21
commits into
stanfordnlp:main
from
chenmoneygithub:react-native-tool-calling
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
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.
Refactor dspy.ReAct to use the dspy.ToolCalls for consistency.
We are keeping the behavior that when JSONAdapter is used with ToolCalls, we direct it to the ChatAdapter for good quality, because we have been consistently noticing that the models are doing poorly when using structured output +
dict[str, Any]
. With our experiments, native tool calling can mitigate this issue, but native tool calling is not producing promising results now, and we are still doing experiments there.Did a quick benchmark on Hover dataset for this PR, and we see a pretty clear quality regression:
My theory is all these LMs are doing a worse job of understanding deep nested output type than flat types. In details,
dspy.ToolCalls
is a nest type that has a list ofdspy.Toolcalls.ToolCall
, which has two fields, one is a string representing the name, and the other representing the arg dict. As a comparison, the current react usesnext_tool_name
, which is a single string, andnext_tool_args
which is a dict. So this PR is introducing too much nesting to keep LM of a decent quality.All benchmarks are done on 50 data from Hover dataset, with ChatAdapter. Benchmark script: