mirror of
https://github.com/MindWorkAI/AI-Studio.git
synced 2026-10-18 08:58:00 +00:00
Added tool calling support (#731)
Co-authored-by: krut_ni <nils.kruthoff@dlr.de> Co-authored-by: Thorsten Sommer <SommerEngineering@users.noreply.github.com>
This commit is contained in:
266 files changed
+11186
-740
No files matched your search
@@ -83,6 +83,7 @@ Each assistant plugin lives in its own directory under the assistants plugin roo
|
||||
- `ASSISTANT` is the root table. Every assistant requires `Title` and `Description`.
|
||||
- Form assistants additionally require `SystemPrompt`, `SubmitText`, `AllowProfiles`, and a nested `UI` definition.
|
||||
- Direct chat launchers instead require `LaunchBehavior = "OPEN_WORKSPACE_CHAT_BY_NAME"` and `WorkspaceName`. AI Studio stops reading the form-only fields as soon as a launch behavior is active, so older launchers that still carry them keep working.
|
||||
- `ToolIds` is optional for both kinds and names the tools the assistant runs with, such as `{"web_search"}`. When present, it must list at least one unique, non-empty tool ID; omit the field instead of writing an empty list. For a form assistant, naming tools takes the choice away from users: the tool selection disappears, and the assistant always runs with exactly these tools. For a launcher, the tools are merely preselected and users may change them once the chat is open. Naming a tool is a wish, not a permission: a tool switched off in the settings stays off, one whose settings are incomplete cannot run, and every tool still has to meet the confidence requirements of the provider in use. A tool ID unknown to the installation is skipped.
|
||||
- `DEPLOYED_USING_CONFIG_SERVER` identifies who manages the assistant plugin. Set it to `false` for locally managed plugins. A missing field is also treated as local for compatibility with existing plugins. Enterprise-distributed plugins must set it to `true` and cannot be revised with AI in AI Studio.
|
||||
- `AI_STUDIO_ASSISTANT_BUILDER = {Generated = true, SchemaVersion = 1}` is reserved for plugins generated by the AI Studio Assistant Builder. It enables Builder-specific actions such as safe deletion and must not be added to manually authored or enterprise-distributed assistants. Newly generated Builder assistants always set `DEPLOYED_USING_CONFIG_SERVER = false` explicitly.
|
||||
- `UI.Type` is always `"FORM"` and `UI.Children` is a list of component tables.
|
||||
@@ -123,6 +124,9 @@ ASSISTANT = {
|
||||
"44444444-4444-4444-4444-444444444444",
|
||||
"55555555-5555-5555-5555-555555555555",
|
||||
},
|
||||
["ToolIds"] = { -- optional; preselects these tools in the opened chat
|
||||
"web_search",
|
||||
},
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
@@ -73,6 +73,19 @@ ASSISTANT = {
|
||||
["SystemPrompt"] = "<prompt that fundamentally changes behaviour, personality and task focus of your assistant. Invisible to the user>", -- required
|
||||
["SubmitText"] = "<label for submit button>", -- required
|
||||
["AllowProfiles"] = true, -- if true, allows AiStudios profiles; required
|
||||
|
||||
-- Optional: the tools your assistant runs with. Naming them takes the choice away from the
|
||||
-- user: the tool selection disappears from the assistant, and it always runs with exactly
|
||||
-- these tools. Omit the field to let users select the tools themselves.
|
||||
-- Naming a tool is a wish, not a permission: a tool switched off in the settings stays off,
|
||||
-- and every tool still has to meet the confidence requirements of the provider in use. Users
|
||||
-- see the tools your assistant asks for before they enable it, and the security audit weighs
|
||||
-- them against what your assistant claims to do.
|
||||
-- Tool IDs include: web_search, read_web_page
|
||||
["ToolIds"] = {
|
||||
"web_search",
|
||||
},
|
||||
|
||||
["UI"] = {
|
||||
["Type"] = "FORM",
|
||||
["Children"] = {
|
||||
@@ -443,4 +456,11 @@ ASSISTANT = {
|
||||
["DataSourceIds"] = {
|
||||
"<optional data source GUID>",
|
||||
},
|
||||
-- Optional: the tools preselected when the chat opens. Users may change the selection
|
||||
-- in the chat afterwards, and every tool has to meet the confidence requirements of the
|
||||
-- provider in use. A tool ID unknown to the installation is ignored.
|
||||
-- Tool IDs include: web_search, read_web_page
|
||||
["ToolIds"] = {
|
||||
"<optional tool ID>",
|
||||
},
|
||||
}
|
||||
Reference in new issue
Block a user