docs: clarify LlmAgent composition for workflow agents#1232
Merged
Conversation
copybara-service
Bot
force-pushed
the
test_922007532
branch
2 times, most recently
from
91756d6 to
a57dd91
Compare
copybara-service
Bot
force-pushed
the
test_922007532
branch
from
a57dd91 to
b9e2599
Compare
Document on ParallelAgent, SequentialAgent, and LoopAgent that they do not transfer control back to an LlmAgent orchestrator after they complete, and that placing the workflow agent and any follow-up agent as siblings inside a SequentialAgent (used as the root or transferred-to agent) is the recommended pattern. This matches the behavior of adk-python v1.x, which is the line that Java ADK currently tracks. A more robust orchestration will be available once Java reaches the Graph Workflows milestone aligned with adk-python v2.0. PiperOrigin-RevId: 922080205
copybara-service
Bot
force-pushed
the
test_922007532
branch
from
b9e2599 to
49ff63b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs: clarify LlmAgent composition for workflow agents
Document on ParallelAgent, SequentialAgent, and LoopAgent that they do
not transfer control back to an LlmAgent orchestrator after they
complete, and that placing the workflow agent and any follow-up agent
as siblings inside a SequentialAgent (used as the root or transferred-to
agent) is the recommended pattern.
This matches the behavior of adk-python v1.x, which is
the line that Java ADK currently tracks. A more robust orchestration
will be available once Java reaches the Graph Workflows milestone aligned
with adk-python v2.0.