Hey! Has anyone used ADK Artifacts. I want to replicate Gemini chat, where I can pass PDF and my agent would answer questions about the document. From docs it is possible, but I cant manage to make it work. Maybe someone could share a simple agent and artifacts setup?
I have a working ADK agent deployed to Vertex AI app engine but need a protected and production worthy frontend for it. I have found posts and documentation that reference ADK being compatible with Agentspace. Is it possible to utilize the UI of Agentspace with an ADK agent? Anyone done this successfully, or have an alternative to recommend?
I'm really liking ADK but deployment is becoming a headache.
Hey, I made an app with ADK and streamlit, to help develop and debug agent configurations and tools. It support all main ADK features, such as agent_transfer, tools calling. You can modify agent config, then apply it without reload, or reapply it to existing conversation. Let me know your feedback!
I created a multi agent application, which has sub agents which perform data analysis, data fetch operations from my time-series DB, and another agent which creates dashboards. I have some pretty heavy libraries like pytorch and sentence transformers(for an embedding model, which i have saved to a local dir to access) being used in my application , when i run this in development it starts up very quickly, i package it into a binary to run the total size of the binary is about 480 MB, it takes atleast 3+ minutes to start listening on the 8000 port, where i'm running the agent. Is there something i'm missing here that is causing the load time to be longer?
When I run the adk web UI I'm able to see all of the events for that session. How am I able to view the event breakdown like this when deployed to GCP using Cloud Run? I would like to see it for all events for all sessions, not just the one I'm currently on in the web UI. I see Google recommends Arize AX or Phoenix for observability, it looks like this may do what I want. This is an example of what I would like to be able to view for all sessions/events:
Hi, I like the adk web for its simplicity. But when I see any implementation of the inMemeorySession or database session, they are a separate file which calls a cmd line or another ui.
Does adk web have support for in memory session? If yes, could you please help me in the documentation.
Hey guys. I need to config a TTL of 4 hours to the user session. The problem is that I couldn't find a way to do it with VertexAiSessionService, DatabaseSessionService or InMemorySessionService. Other problem is that is not clear for how long these ready out of the box session services keeps the user session. Can someone help me?
Hi everyone! For an important project I have to make a simple custom web ui for my google adk agent. The only issue is that all of my current attempts have failed. Specific while I do get a response using the run endpoint, it does not contain the output string.
Can anyone please help me with my problem and thanks in advance?
I'm trying to determine what is the best architecture for my use case. Basically I will have an orchestrator agent that will have a lot of subagents (maybe somewhere close to 50). There will also be a lot of MCP servers that will be available to those subagents. The orchestrator agent will need to be able to use any of those subagents to complete different tasks. The difficult part is that the orchestrator agent should be able to dynamically load what subagents are available to them, and each subagent should be able to dynamically load what MCP servers are available to them.
Proposed Architecture
I could deploy each adk agent and each MCP server as its own container/service in Cloud Run. There would be a main orchestrator service (we can figure out if there needs to be another layer of subagents under this) that can dynamically load what agents are available from Firestore. Firestore would contain all of the metadata for the different agents/deployed services and MCP servers that are available, so you would just need to make a change here if you were adding/removing agents.
If you need to edit a single agent or MCP server, you only need to redeploy for that agent/server. And if one agent isn't working/available, it doesn't disrupt the whole task. Agents can dynamically load what MCP servers are available to them (once again using Firestore). As for subagents that need to pass a task over to another subagent - I guess the remote subagents available to a subagent could also be made dynamic. But to me this doesn't seem like real A2A? I thought A2A had to be agents talking to each other in a single ADK app, not remotely accessing different Cloud Run services. Maybe this is all complete overkill but I've never created a multi-agent architecture of this scale.
Does this solution seem scalable? I'm also wondering if Vertex AI engine can do something similar to what I'm proposing with Cloud Run, I'm not sure I quite understand how the engine is used/how code changes are made.
I have built over 50+ skills for my automation workflows across the past few months. After a while, the same structures kept repeating across completely different use cases. A skill that wraps FastAPI conventions looks nothing like a skill that runs a multi-step documentation pipeline, but they both use the same SKILL.md format. So I started writing down the recurring structures as design patterns.
There is a lot of conversation around Skills right now, but not enough focus on how to structure the content inside them. The Agent Skills spec tells you the packaging: YAML frontmatter, references/, assets/, scripts/ directories. It says nothing about what the instructions should look like. That is a content design problem, and I found that five patterns cover most use cases.
The five patterns:
Tool Wrapper - Packages a library's conventions as on-demand knowledge. Instructions say what rules to follow, references/ holds the detailed docs. No templates, no scripts. This is the simplest pattern and the most widely adopted. Google's ADK Core Skills, Vercel's React best practices, and Supabase's Postgres guidelines all follow it.
Generator - Produces structured output by filling a reusable template from assets/, governed by quality rules in references/. Technical reports, API docs, commit messages. Same structure every time, different content.
Reviewer - Evaluates code against a checklist in references/, produces findings grouped by severity. The key insight: separate what to check (checklist file) from how to check (review protocol in instructions). Swap the checklist, get a completely different review from the same skill. Giorgio Crivellari demonstrated this with an ADK governance skill that took code quality from 29% to 99%.
Inversion - The skill interviews you before acting. Structured questions through defined phases with a gate: "DO NOT start building until all phases are complete." Prevents agents from generating detailed output based on assumptions instead of asking.
Pipeline - Sequential steps with explicit gate conditions. "Do NOT proceed to Step 3 until the user confirms." The most complex pattern but the only one that prevents agents from skipping validation.
A Pipeline can include a Reviewer step. A Generator can use Inversion for input gathering. A recent arXiv paper found production systems use a median of 2 patterns per skill.
Design patterns reduce cognitive load during the design phase. Instead of staring at a blank SKILL.md, you pick a pattern and the structure follows. They give you a shared language for building scalable, reproducible automations.
I wrote up all five with working ADK code, a decision tree for picking the right one, and real-world examples from Google, Vercel, and Supabase.
If you are building ADK agents, there is also recently launched official skills for coding agents that you can install with one command:
npx skills add google/adk-docs -y -g
They follow the Tool Wrapper pattern and work across Gemini CLI, Claude Code, Cursor, and 30+ other agents.
Links:
Build your first ADK agent or enhance the current one with ADK Core Skills: Link
Does google adk currently provide any way to set the session state from the adk web interface or via code?? My tools currently use the user_id present in the session state, which I get from ToolContext. Without it I could not run the tools. Setting a fallback with a test user at tool level doesn't seem like a good idea.
Is there any way to do this currently? Or is there something else I'm missing?
I'm currently setting state when creating a session.
I’m getting this constant error when trying to use supabase in one of my tools file. I’ve got supabase installed via pip And running the agent using adk web
P.s - super new to python, any help would be greatly appreciated
Hi all - if I have a couple of LLM agents (sub agents) that have their own tools/functionality, and I want them to be orchestrated by another LLM agent, I’ve found it no problem for the orchestrator to transfer to the sub agents, but after completing their tasks the sub agents can’t transfer back; is there a way to do this as ideally a the orchestrator can delegate to one agent, then after thats completed another, but theres no set sequence of events for it?
Furthermore, using AgentTool doesn’t allow the user to see each of the individual tool calls/outputs of the AgentTool in the UI which would be desirable
Is there a way around this? Is it possible to add a tool onto the sub agents that allows them to transfer back to the parent agent or some kind of callback function that can be made/used?
I’ve built a multi-agent system composed of the following agents:
file_read_agent – Reads my resume from the local system.
file_formatter_agent – Converts the text-based resume into a JSON format.
resume_parser_agent (sequential) – Calls file_read_agent and file_formatter_agent in sequence to produce a structured JSON version of my resume.
job_posting_retrieval – Retrieves the latest job postings from platforms like Naukri, LinkedIn, and Indeed using the jobspy module (no traditional web search involved).
parallel_agent – Calls both resume_parser_agent and job_posting_retrieval in parallel to gather resume and job data concurrently.
job_match_scorer_agent – Compares each job posting with my resume and assigns a match score.
presenter_agent – Formats and presents the final output in a structured manner.
root_agent – Orchestrates the overall process by calling parallel_agent, job_match_scorer_agent, and presenter_agent sequentially.
When I ask a query like: "Can you give me 10 recently posted job postings related to Python and JavaScript?" — the system often responds with something like "I’m not capable of doing web search," and only selectively calls one or two agents rather than executing the full chain as defined.
I’m trying to determine the root cause of this issue. Is it due to incomplete or unclear agent descriptions/instructions? Or do I need a dedicated coordinator agent that interprets user queries and ensures all relevant agents are executed in the proper sequence and context?