⚡ Bolt: Concurrent LLM Tool Execution in Pipelines

[ishaanxgupta]

💡 What: Refactored LLM tool execution loops in RetrievalPipeline.run, CodeRetrievalPipeline.run, and CodeRetrievalPipeline.run_stream to use asyncio.gather() for concurrent dispatch of individual tool queries.

🎯 Why: Previously, if the LLM returned multiple tool calls (e.g., searching the profile, temporal, and code namespaces), they were executed sequentially. Because each search involves external vector and/or graph database calls, executing them in series created a significant linear latency bottleneck.

📊 Impact: Expect a noticeable reduction in total response latency (Time to Last Byte) when the LLM triggers multiple tools simultaneously. Latency is now bound by the slowest individual tool call rather than the sum of all tool calls.

🔬 Measurement: This improvement can be verified by asking complex, multi-domain queries (e.g., "What bugs did I fix today and what did I eat for lunch?") and measuring the total retrieval latency. It's visible in the logs: total time between "Tool call" and "Tool results" will shrink.

---

PR created automatically by Jules for task 1081248673563426961 started by @ishaanxgupta

[google-labs-jules]

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.