Connect to Remote Agents with ADK and the Agent2Agent (A2A) SDK Reviews

Pravallika N. · Reviewed 24 يوم ago

Garvita V. · Reviewed 24 يوم ago

Nice

Ajay k. · Reviewed 24 يوم ago

stuck at adk web, no clear instruction where to change the authuser, i tried changing multiple times and it didnt work. Had to do lab using adk run

Arushi R. · Reviewed 24 يوم ago

Akhil P. · Reviewed 24 يوم ago

Getting errors only treid everything 00 OK INFO: 127.0.0.1:53800 - "POST /apps/illustration_agent/users/user/sessions HTTP/1.1" 403 Forbidden 2026-03-24 19:14:35,427 - INFO - local_storage.py:60 - Creating local session service at /home/student_02_769af13ec822/adk_and_a2a/illustration_agent/.adk/session.db INFO: 127.0.0.1:53800 - "GET /apps/illustration_agent/users/user/sessions HTTP/1.1" 200 OK INFO: 127.0.0.1:53800 - "POST /run_sse HTTP/1.1" 403 Forbidden INFO: 127.0.0.1:53800 - "GET /debug/trace/session/ HTTP/1.1" 307 Temporary Redirect INFO: 127.0.0.1:53800 - "GET /debug/trace/session HTTP/1.1" 404 Not Found

Bhanu P. · Reviewed 25 يوم ago

i got an error forbidden 403 on this lab

Megha S. · Reviewed 25 يوم ago

facing issue to compete task2, as per guided still throws same error for 403 and changed to authuser-2 respectively. the .env file doesnot get filled with respectve environment and facing issue of 403, 404,307

Ruchita H. · Reviewed 25 يوم ago

Kavish N. · Reviewed 25 يوم ago

Getting forbidden error and unable to resolve it

Venkatesh B. · Reviewed 25 يوم ago

Shreetama B. · Reviewed 25 يوم ago

I kept getting a 403 error which did not get fixed with the given instructions in the codelabs

Amartya G. · Reviewed 25 يوم ago

things are not working

Prashanth reddy G. · Reviewed 25 يوم ago

The lab content is good in theory, but the execution experience is very frustrating. I followed all the steps carefully and was able to successfully start the server and open the ADK UI. However, the agent did not respond to any prompts. The terminal consistently showed "403 Forbidden" errors for session-related endpoints (such as /users/user/sessions and /run_sse), which completely blocked progress. This appears to be an authentication/session issue in the lab environment rather than a mistake in following instructions. The lab seems highly sensitive to account/session configuration, but this is not clearly explained. Additionally, the troubleshooting guidance provided (e.g., modifying the URL using "authuser") was not applicable in my case because the URL did not include any "authuser" parameter. This made it even more confusing, as the suggested fix could not be applied. As a result, I spent most of the lab time debugging environment and authentication issues instead of learning the intended concepts. Suggestions: * Clearly instruct users to use a single Google account or incognito mode from the beginning * Provide accurate and applicable troubleshooting steps (especially for 403 errors) * Ensure instructions match the actual URLs and environment behavior * Improve session handling to make the lab more stable and beginner-friendly Overall, the concept is valuable, but the technical issues significantly reduce the learning experience.

Mehhuu Y. · Reviewed 25 يوم ago

403 error coming up, authuser doesnot resolves the issue

Harsh M. · Reviewed 25 يوم ago

shreyash w. · Reviewed 25 يوم ago

Aditya Raj S. · Reviewed 25 يوم ago

Sai Nireeksha M. · Reviewed 25 يوم ago

getting Forbidden Error 403 and it is not solving so cannot complete the tasks. lost 21 credits because of that

Rupal K. · Reviewed 25 يوم ago

Shahid G. · Reviewed 25 يوم ago

Unable to complete task 2 and 4 due to repeated 403 error, even after trying the suggested workaround.

Lalit K. · Reviewed 25 يوم ago

sakshi g. · Reviewed 25 يوم ago

Vinamra J. · Reviewed 25 يوم ago

lab not working in cloud console. Unable to get the output

DEEPAK K. · Reviewed 25 يوم ago

Kundan K. · Reviewed 25 يوم ago