feat: concurrent tools execution #869
Merged
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.
Description
This PR adds concurrent tool execution, allowing independent tools to run in parallel instead of sequentially. This significantly reduces latency when LLMs execute multiple tools that perform I/O operations like API calls or database queries.
Tools can be marked with
->concurrent()to execute in parallel:When an LLM calls both tools, they execute simultaneously instead of sequentially, reducing total execution time from (the slowest tool's duration).
The implementation uses Laravel's Concurrency driver, preserves event ordering in original tool call order. Works with both streaming and non-streaming responses.
Breaking Changes
None. This feature is fully backward compatible and opt-in. All existing tools continue executing sequentially by default.