-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(langchain/createAgent): tools in ModelRequest back to tool instance #9119
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
* The tools to make available for this step. | ||
*/ | ||
tools: string[]; | ||
tools: (ServerTool | ClientTool)[]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does JS already define ServerTools?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really it is very broad defined, e.g. as Record<string, unknown>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! I'll make a corresponding change
We've decided to keep
tools
inModelRequest
a list of tool instances so users have access on more tool information. This also removestools
andtoolCalls
from runtime as it differs from our middleware designs.