Customizable User ID in Google ADK Web Chat Interface

[darkmars27]

** Please make sure you read the contribution guide and file the issues in the right place. ** Contribution guide.

Is your feature request related to a problem? Please describe. Currently, the Google ADK web chat interface hardcodes the user ID to "user". This limitation prevents us from effectively leveraging the existing web chat interface for scenarios involving multiple distinct users, such as gathering feedback from different individuals or simulating various user interactions. To collect diverse feedback or conduct more comprehensive testing, we are forced to develop entirely separate chat interfaces, which is an unnecessary duplication of effort and increases development overhead.

Describe the solution you'd like I would like the ability to customize the user ID in the Google ADK web chat interface. Ideally, this functionality could be implemented through one or more of the following methods:

Query String Parameter: Allow the user ID to be passed as a query string parameter in the URL (e.g., your-adk-web-chat-url?userId=john_doe). Cookie: Enable setting the user ID via a browser cookie, which would persist across sessions. JavaScript API: Provide a JavaScript API call that allows programmatic setting of the user ID before or during the chat session. This would allow us to easily differentiate between user interactions and collect feedback specific to individual users, significantly enhancing the utility of the existing web chat interface.

Describe alternatives you've considered The primary alternative considered is building entirely new custom chat interfaces for each scenario where differentiated user feedback is required. This involves:

Increased Development Time: Significant effort in setting up new UI, backend integrations, and managing separate deployments. Maintenance Overhead: More codebases to maintain and update. Redundant Functionality: Replicating the core chat interface functionality that already exists within the ADK web component.

Another less ideal alternative would be to manually modify the ADK web component's source code to change the hardcoded user ID, but this is not sustainable, easily maintainable, or recommended for production environments due to potential conflicts with future updates.

Additional context Add any other context or screenshots about the feature request here. This feature would be particularly beneficial for:

User Feedback Collection: Allowing multiple internal or external testers to provide feedback through the same interface, with their contributions clearly identifiable by their unique user IDs.

[wyf7107]

Hi, thanks for the feedback, we have an action item to include this feature, stay tuned!

[askmeegs]

+1. Because the Vertex AI Memory Bank integration relies on the user_id, can effectively only store memories for one user at a time when using ADK Web. https://google.github.io/adk-docs/sessions/memory/#how-memory-works-in-practice

[pinkponk]

+1 because I use this to debug for other users than 'user'

[chanchalchitwan]

This is very much required for debugging for different users.

[silva-raphael]

We REALLY need this. Our customer is asking for ways to measure the real active users in order to measure the total ROI. Extremely needed feature!!!