Add Batch tool call for calling multiple tools (#27621)
<img width="620" alt="Screenshot 2025-03-27 at 2 29 13 PM" src="https://github.com/user-attachments/assets/dd023507-61bc-4722-a095-f65f4b6c746a" /> We'll iterate on the UI, but first the goal is to just get it to work at all so we can see if it's useful in terms of getting correct output faster. Release Notes: - N/A --------- Co-authored-by: Agus Zubiaga <hi@aguz.me>
This commit is contained in:
parent
61be869352
commit
56eb650f09
4 changed files with 314 additions and 0 deletions
9
crates/assistant_tools/src/batch_tool/description.md
Normal file
9
crates/assistant_tools/src/batch_tool/description.md
Normal file
|
@ -0,0 +1,9 @@
|
|||
Invoke multiple other tool calls either sequentially or concurrently.
|
||||
|
||||
This tool is useful when you need to perform several operations at once, improving efficiency by reducing the number of back-and-forth interactions needed to complete complex tasks.
|
||||
|
||||
If the tool calls are set to be run sequentially, then each tool call within the batch is executed in the order provided. If it's set to run concurrently, then they may run in a different order. Regardless, all tool calls will have the same permissions and context as if they were called individually.
|
||||
|
||||
This tool should never be used to run a total of one tool. Instead, just run that one tool directly. You can run batches within batches if desired, which is a way you can mix concurrent and sequential tool call execution.
|
||||
|
||||
When it's possible to run tools in a batch, you should run as many as possible in the batch, up to a maximum of 32. For example, don't run multiple consecutive batches of 10 when you could instead run one batch of 30.
|
Loading…
Add table
Add a link
Reference in a new issue