files for creating a new tool (instead of a deprecrated plugin) #3740
Replies: 2 comments 5 replies
-
Please see #3607 Creating tools will actually remain very much the same, as those current tools you listed are going to be backwards compatible:
|
Beta Was this translation helpful? Give feedback.
-
I've copied
docker compose down, up. then, in manifest.json, I've removed the entry about "Stable Diffusion", What can be the issue? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I need to create a plugin/tool. I see that plugins are deprecreated. Is there a doc about creating a tool?
I only see this doc, which seems about deprecated plugins: https://www.librechat.ai/docs/development/tools_and_plugins
What files do I need to create/modify in order to create a Tool?
The TavilySearch is a good example to mimic? (it is a tool, not a plugin?)
the actual tool
testing/spec
all these files need to be updated with the new tool? or some are for tools and others are for plugins?
and configuration in:
TavilySearch has only one function (with several parameters). My tool has several functions. Do I need to create a new tool for each function, or I can combine all the functions into one tool? What is the best existing example to mimic (AzureAISearch.js, ChatTools.js, DALLE3.js, TavilySearchResults.js...)?
Also, how can I enable the tool in the configuration, instead of manually setting up the tool in the web console, Assistants -> Create Assistant -> Add Tool?
Beta Was this translation helpful? Give feedback.
All reactions