⚡ Bolt: Parallelize tool execution - #3
Conversation
This change modifies the agent loop to execute multiple tool calls from a single LLM response concurrently. This significantly reduces latency when multiple tools are invoked (e.g., parallel web searches). - Use `sync.WaitGroup` to execute tools in parallel. - Collect results and preserve original order for deterministic conversation history. - Ensure thread safety in `RuntimeMetrics` by holding the lock during file persistence to prevent race conditions and file corruption. - Add regression test `internal/agent/loop_parallel_test.go`. Co-authored-by: MEKXH <59291264+MEKXH@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Parallelized tool execution in the agent loop.
🎯 Why: Multiple tool calls (e.g., search for X, search for Y) were executed sequentially, causing unnecessary latency.
📊 Impact: Reduces total execution time to approximately the duration of the longest single tool call + overhead.
🔬 Measurement: Added
internal/agent/loop_parallel_test.gowhich shows a drop from ~300ms to ~100ms for 3 concurrent 100ms tasks.PR created automatically by Jules for task 10507193342825563532 started by @MEKXH