Liang Wu
98896eb2aa
A streaming tool used to only talk to the model: every value it yielded came back as a FunctionResponse. Therefore it costs model context and could derail the model's reasoning. An Event with message yielded by a streaming tool is now addressed to the user instead. It is enqueued on the invocation's event queue, so the runner appends it to the session and streams it to the client, and it is never sent over the live model connection. Plain values are still sent to the model as FunctionResponse. A tool can mix and match any number of each, in any order. Runner's run_live also now initializes the invocation's event queue and merges it with the live agent's own event stream. Without a queue, anything running under the live agent that enqueues an event -- a streaming tool, or a node -- fails with "_event_queue is not set". Co-authored-by: Liang Wu <wuliang@google.com> PiperOrigin-RevId: 968533249
Contributing Resources
This folder hosts resources for ADK contributors, for example, testing samples etc.
Samples
Samples folder host samples to test different features. The samples are usually minimal and simplistic to test one or a few scenarios.
Note: This is different from the google/adk-samples repo, which hosts more complex e2e samples for customers to use or modify directly.
ADK project and architecture overview
The adk_project_overview_and_architecture.md describes the ADK project overview and its technical architecture from high-level.
This is helpful for contributors to understand the project and design philosophy. It can also be fed into LLMs for vibe-coding.