You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VertexAISearchTool using Google Drive data store does not return results to Dev UI unless streaming is enabled #1604
** Please make sure you read the contribution guide and file the issues in the right place. ** Contribution guide.
Describe the bug
If you connect to a Vertex AI Search data store using the VertexAISearchTool and query it from an agent in the Dev UI, it will appear as though the interface has frozen (agent response dots repeating infinitely).
The search results have been returned, and you can see them in the Terminal pane where the adk web Dev UI has been run. If you use adk run on the agent instead, you can see the results returned and the agent response. If you enable streaming within the adk web dev ui, you can also see the results return.
But without streaming, it just hangs.
To Reproduce
Steps to reproduce the behavior:
Create a vertex AI data store (I used unstructured data in Google Drive)
In an agent, add the VertexAISearchTool, like so:
from google.adk.tools import VertexAiSearchTool
# The data_store_id path follows the same format as the datstore parameter
# of google.genai.types.VertexAISearch. View its documentation here:
# https://googleapis.github.io/python-genai/genai.html#genai.types.VertexAISearch
# Create your vertexai_search_tool and update its path below
vertexai_search_tool = VertexAiSearchTool(data_store_id="projects/YOUR_PROJECT_ID/locations/global/collections/default_collection/dataStores/YOUR_DATA_STORE_ID")
Add the tool to an agent and ask it questions about the data store using adk run, and adk web with and without streaming.
See that without enabling streaming, it will not return a response in the dev UI
Expected behavior
A response grounded on the data store.
Hi @andrewlarimer and thanks to everyone who participated in this thread.
We're currently doing some housekeeping on our issue tracker. Given the rapid pace of development and the number of updates since this was last active, there's a good chance this issue has been resolved in a newer version. To help us keep our backlog focused on current issues, we are closing this as stale.
If you're still facing this problem, could you please update to the very latest version of the library and confirm the issue still exists? If it does, please comment here, and we will be happy to reopen this issue and investigate further.
Activity
kssrinivasan commentedon Jun 23, 2025
I have seen the exact same behavior. Reported in google/adk-web#65.
surajksharma07 commentedon Oct 8, 2025
Hi @andrewlarimer and thanks to everyone who participated in this thread.
We're currently doing some housekeeping on our issue tracker. Given the rapid pace of development and the number of updates since this was last active, there's a good chance this issue has been resolved in a newer version. To help us keep our backlog focused on current issues, we are closing this as stale.
If you're still facing this problem, could you please update to the very latest version of the library and confirm the issue still exists? If it does, please comment here, and we will be happy to reopen this issue and investigate further.
Thanks for your contribution and understanding!